[3/4] Properly cleanup unclosed files within generator function #910
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a case that
file.close
is never called because when generator function has never reached to the end. A simple example would bezip
two datepipes with different length. The longer DataPipe would never reach the end of generator and then it will be cleaned up bygc
. So, the line offile.close
is not executed. (This is the reason that Vitaly has to create this hack to retrieve all remaining data to make sure generator function is fully executed)However, this hack introduces another problem where an infinite datapipe would make
zip
never end as it would try to deplete the infinite iterator. See: #865So, in this PR, I am adding a
try-finally
clause to make sure thefile.close
is always executed during the destruction ofgenerator
object. Then, we don't need the hack withinzip
any more.