This tutorial helped me, thanks! I couldn't grasp how Python just KNOWS that it should "open" and "close" the file, especially if it just KNOWS how to do these entry and exit functions for any other command that "with" is compatible with. I finally got it. In the file() example, file.open and file.close are versions of the generalized functions of "__enter__" and "__exit__," which are functions that exist in all sorts of python modules. "with" works by doing the "__enter__" and "__exit__" functions automatically. I feel like all the other tutorials I tried before this could start by saying that single sentence and everyone would say "Ohhhh".
I am now going to write context managed classes for connection objects. Love this! Note: one can write code to open a file, then read/write a file, but may or may not remember to close the file, and even if they do close the file, it's less likely to be done in a 'finally:' clause, so there is no guarantee it will be closed. The point is, try/finally wouldn't even get used for open/close (because people can write bad code, and it still seems to 'work'). This is why we have a context manager: to make python play nice with the OS. Also, I think the contextmanager decorator code communicates what it is better than the class code, even to someone who may not well understand decorators and generators.
2:58 The important reason for calling close() (or flush()) on an *output* file is so that you catch any I/O errors on the writes. Otherwise you could suffer loss of data without realizing it! Consider this littie script: f = open("/dev/full", "w") f.write("junk") That should raise “OSError: [Errno 28] No space left on device”, but because the script exits before the file is properly closed, you never see that. This version, on the other hand with open("/dev/full", "w") as f : f.write("junk") #end with does properly raise the error. As does f = open("/dev/full", "w") f.write("junk") f.close() but the with-statement version guarantees to flush the output even if some exception occurs before getting to the end.
I believe you should put the line where you open the file outside of the try statement. Otherwise, if the file doesn't exist, an error is raised, and in addition in finally you call the close on the file handler var which wasn't created. As a result, 2 errors raised.
probably it's incorrect that after with statement the object closes. Because when we use "with tensorflow.GradientTape() as tape:" we use tape even beyond the with statement.
3:33 Really the only situation where you could leak resources is when you are accessing some low-level API, for example via ctypes. In this case the calls you are making are equivalent to what you would do in a lower-level language like C, where you have to explicitly allocate and free all dynamic resources. The best thing to do in this situation is to create a Python wrapper for the lower-level C API, so the objects implemented by that API are represented by high-level Python objects that automatically manage their own resources just like any other Python object. In the wrapper you might use with-statements, try-finally blocks, and of course the __del__ method for making sure the lower-level resource-freeing calls are invoked before the Python object disappears.
Very interesting! I got a little confused on the last example though xD Is not the decorator already closing the file, making the f.close() inside managed_file function a little redundant?
2:27 That’s not a reason for using a with-statement. Remember that *all* Python objects keep track of their resources anyway, and free them when they disappear. And CPython is reference-counted, so this happens immediately the last reference to an object goes away.
Noob question -- can I use my own function in the statement and it operates normally? Like, def my_function( ): complex junk here with open('file') as fileObj: my_function( )
in this case, what purpose does opening the file serve? calling open('file') is effectively checking whether the file exists, yielding it and closing it without changing it. unless the "complex junk" manipulates said file, which opens another can of worms where the file is referenced before it is opened, let alone that my_function takes no parameters and thus *cannot* know what file you're referring to.
Maybe you should close the video by saying: "Use the 'with open' syntax to optimize your file opening code realizing what's going on structurally within python"
What is it exactly that highlights syntax in your python console? I see this is explained in your other video clip: m.th-cam.com/video/cg_3E3Cb3MA/w-d-xo.html Thank you for both! You’re a star!
![[LIVE] : ONE ลุมพินี 82 วันนี้!! คู่เอก | ยอดไอคิว vs อับดัลลาห์](http://i.ytimg.com/vi/hSsyTl_9bqs/mqdefault.jpg)
This tutorial helped me, thanks! I couldn't grasp how Python just KNOWS that it should "open" and "close" the file, especially if it just KNOWS how to do these entry and exit functions for any other command that "with" is compatible with. I finally got it. In the file() example, file.open and file.close are versions of the generalized functions of "__enter__" and "__exit__," which are functions that exist in all sorts of python modules. "with" works by doing the "__enter__" and "__exit__" functions automatically. I feel like all the other tutorials I tried before this could start by saying that single sentence and everyone would say "Ohhhh".
This is the best god damn video on the "with" statement I have ever seen.
Thanks! I'm glad you enjoyed it.
2019 still best explanation on the web.
2020, same is true
2021 and still
This saved me a whole line of code, and for that I'm grateful
really excellent. one of the clearest technical explanations i've seen
I am now going to write context managed classes for connection objects. Love this!
Note: one can write code to open a file, then read/write a file, but may or may not remember to close the file, and even if they do close the file, it's less likely to be done in a 'finally:' clause, so there is no guarantee it will be closed.
The point is, try/finally wouldn't even get used for open/close (because people can write bad code, and it still seems to 'work'). This is why we have a context manager: to make python play nice with the OS.
Also, I think the contextmanager decorator code communicates what it is better than the class code, even to someone who may not well understand decorators and generators.
Randomly I ended up here found this too good. Now I am gonna watch all of these.
I'm glad you enjoyed the video!
2021 still the best explanation on the web.
17 March 2020 - One word, Amazing and thanks!
2:58 The important reason for calling close() (or flush()) on an *output* file is so that you catch any I/O errors on the writes. Otherwise you could suffer loss of data without realizing it!
Consider this littie script:
f = open("/dev/full", "w")
f.write("junk")
That should raise “OSError: [Errno 28] No space left on device”, but because the script exits before the file is properly closed, you never see that. This version, on the other hand
with open("/dev/full", "w") as f :
f.write("junk")
#end with
does properly raise the error. As does
f = open("/dev/full", "w")
f.write("junk")
f.close()
but the with-statement version guarantees to flush the output even if some exception occurs before getting to the end.
I was just wondering about this the other day. Super clear explanation. Thanks!
You're welcome!
This is way more helpful than the stack overflow page. Thanks
Cheers, it makes me really happy to hear that :-)
Great explanation, with the user defined class and all. Thank you!
I believe you should put the line where you open the file outside of the try statement. Otherwise, if the file doesn't exist, an error is raised, and in addition in finally you call the close on the file handler var which wasn't created. As a result, 2 errors raised.
Thanks for sharing your thoughts on this!
Which REPL are you using in the video? It looks awesome, is it ptpython?
Wow, I'm really thankful for your explanation!
Nicely explained sir. I'm ur new subscriber. Thanks a lot for this vedio.
Really helpful. Thanks for the video. One question. Is there any performance loss in this approach ?
Excellent!!! Nice and clear
probably it's incorrect that after with statement the object closes. Because when we use "with tensorflow.GradientTape() as tape:" we use tape even beyond the with statement.
Hi, thank you very much. Your videos are really helpful. Well explained! Kudos to you.
Thanks Mushfiqur, I really appreciate it! Happy Pythoning!
3:33 Really the only situation where you could leak resources is when you are accessing some low-level API, for example via ctypes. In this case the calls you are making are equivalent to what you would do in a lower-level language like C, where you have to explicitly allocate and free all dynamic resources.
The best thing to do in this situation is to create a Python wrapper for the lower-level C API, so the objects implemented by that API are represented by high-level Python objects that automatically manage their own resources just like any other Python object. In the wrapper you might use with-statements, try-finally blocks, and of course the __del__ method for making sure the lower-level resource-freeing calls are invoked before the Python object disappears.
no such thing as ideal or enough or not, any is ok, no such thing as easy or not lifex, ts just toolx doesn't matter. ts not communicx or not
Very interesting! I got a little confused on the last example though xD
Is not the decorator already closing the file, making the f.close() inside managed_file function a little redundant?
2:27 That’s not a reason for using a with-statement. Remember that *all* Python objects keep track of their resources anyway, and free them when they disappear. And CPython is reference-counted, so this happens immediately the last reference to an object goes away.
tks, it helps a lot
Great man. Like your vdeos so much. Help me a lot
Beautifully done. Do the mugs on your site support you?
Thank you! Yes, the mugs do help support me, they are also great for some unique Python Swag! :-)
I'm not native, what's a swag? And what's mug in the context you're referring to
nerdlettering.com/?ref=dbaderorg
I enjoy your videos and I will be looking for your book(s).
Thanks bro
with explaind as very return well # (It's very pythonic!)
thanks!
yield versus return. what is the difference?
how do you get terminal code prompts and suggestions like in the video? could it do that on pycharm terminal and console?
Thanks...
Nice video, thanks!
You're welcome!
What do you mean by "leak resources" by not using with?
Thank you so much!
You're welcome!
why '',' operator using in the assignment like d,=4 or return d,
What is the point of "f"?
Hi Dan,
do you plan to release a printed version of your book in the future?
Thanks!
which code editor is this??
In my case, the program sometimes RANDOMLY outputs the keys with the ASCII table form.
Ex: "\x08" pressed
sometimes it works ok. anyone knows why
This video stucks after few seconds. Doesn't move after about 40sec. Kindly upload again.
The video appears to be working fine on our end, are you able to try another web browser? This may resolve the problem.
Hello Dan. Thanks for replying. It's is playing smoothly.
Could you please tell me how the ,, exit file " would work after that I have written "printed" an output to a text file ?
Thanks in forward :)
It releases the handle to the garbage collection heap, so the memory is free again. FREEDOM!
Noob question -- can I use my own function in the statement and it operates normally?
Like,
def my_function( ):
complex junk here
with open('file') as fileObj:
my_function( )
in this case, what purpose does opening the file serve? calling open('file') is effectively checking whether the file exists, yielding it and closing it without changing it. unless the "complex junk" manipulates said file, which opens another can of worms where the file is referenced before it is opened, let alone that my_function takes no parameters and thus *cannot* know what file you're referring to.
Maybe you should close the video by saying: "Use the 'with open' syntax to optimize your file opening code realizing what's going on structurally within python"
What is it exactly that highlights syntax in your python console? I see this is explained in your other video clip: m.th-cam.com/video/cg_3E3Cb3MA/w-d-xo.html Thank you for both! You’re a star!
The only generators I like, are those who generate money........
the video image is too poor, you need to fix it more
with Much(love):
me.thank(you)
OMG, use an IDE for crying out loud
Using yield does not make it a generator, but is just a "hack" to keep the local state active