-
-
Notifications
You must be signed in to change notification settings - Fork 34.5k
gh-89727: Fix os.walk to handle late editing of dirs #100703
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from 1 commit
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
2767f70
adopt old os.walk behavior to handle changes to dirs list after itera…
jonburdo 04a16a2
move stack logic to bottom of loop in os.walk
jonburdo 6b0465f
move scandir logic to bottom of loop
jonburdo 2ff800f
use for-loop to process dirs in bottom-up clause
jonburdo 072bdfb
Merge branch 'main' into os-walk-dirs-editing
jonburdo 41d7463
return if scandir_it fails on first value
jonburdo d81ff45
add test for late modification of dirs in os.walk
jonburdo 431d47a
Merge branch 'main' into os-walk-dirs-editing
jonburdo 2829a7d
use while-else instead of while True, make variable names clearer
jonburdo b59358b
change os.walk docstring to say "traverse" instead of "recurse"
jonburdo 839f31e
fix scandir comment
jonburdo 1011e19
Merge branch 'main' into os-walk-dirs-editing
jonburdo 80b7e82
split topdown and bottomup logic into separate functions for os.walk
jonburdo 70cb0c2
Merge branch 'main' into os-walk-dirs-editing
erlend-aasland File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
move stack logic to bottom of loop in os.walk
- Loading branch information
commit 04a16a22f5c7cd969c46e9a0c510e66f86bfc432
There are no files selected for viewing
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
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 was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Such a high percentage of code in this function is now under either
if topdownor the reverse that I'm kind of curious what it would look like to just have separate (internal) functions for topdown vs bottom-up. But this would still increase code duplication significantly, and move the duplicated code/structure further apart, so I suspect it's still better this way.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was actually thinking about this. I just gave it a shot to see. This seems to me like one of those cases where there are enough little differences in logic that it's much cleaner to separate the two. If we didn't support dir modification for topdown or didn't care about performance it might be simpler, but when you have a lot of the same logic interspersed by a lot of little differences it gets messy. In these kinds of situations I also tend to prefer some duplication between functions over one big function with conditions inside of loops.
I also find it easier to look at the two sets of logic separately, but either way works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I think the split version seems fine. Will wait a bit and see if some core devs have opinions.