mirror of
https://github.com/python/cpython.git
synced 2025-08-03 16:39:00 +00:00
I was confused before. It's correct to not call .close() inside the with
statement, but add a comment that clarifies the purpose of the code.
This commit is contained in:
parent
173d4109b5
commit
d8f870d0fa
1 changed files with 3 additions and 2 deletions
|
@ -259,11 +259,12 @@ Functions and classes provided:
|
|||
|
||||
with ExitStack() as stack:
|
||||
files = [stack.enter_context(open(fname)) for fname in filenames]
|
||||
close_files = stack.pop_all().close()
|
||||
# Hold onto the close method, but don't call it yet.
|
||||
close_files = stack.pop_all().close
|
||||
# If opening any file fails, all previously opened files will be
|
||||
# closed automatically. If all files are opened successfully,
|
||||
# they will remain open even after the with statement ends.
|
||||
# close_files() can then be invoked explicitly to close them all
|
||||
# close_files() can then be invoked explicitly to close them all.
|
||||
|
||||
.. method:: close()
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue