Fix minor issues in OSFS.scandir #475
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
Type of changes
Checklist
Description
Since Python 3.6,
os.scandirreturns an object that must be explicitly closed if the iteration stops before the iterator is exhausted. This PR does that, which should suppressResourceWarningthat were occasionally raised by an unclosed iterator inOSFS.scandir. I also changed the currentOSFS.scandircode so that it only callsstatwhen necessary. Closes #311 .I made it so
tests.test_osfs.TestOSFSnow treats warnings as errors, but it's still not 100% feasible to test this kind of warnings, because they are thrown on garbage collection, most of the time after our test case has finished running.