Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
GH-77609: Add recurse_symlinks argument topathlib.Path.glob()
#117311
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
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
Replace tri-state `follow_symlinks` with boolean `recurse_symlinks`argument. The new argument controls whether symlinks are followed whenexpanding recursive `**` wildcards. The arguments correspond as follows: follow_symlinks recurse_symlinks =============== ================ False N/A None False True True
diegorusso pushed a commit to diegorusso/cpython that referenced this pull requestApr 17, 2024
python#117311)Replace tri-state `follow_symlinks` with boolean `recurse_symlinks` argument. The new argument controls whether symlinks are followed when expanding recursive `**` wildcards. The possible argument values correspond as follows: follow_symlinks recurse_symlinks =============== ================ False N/A None False True TrueWe therefore drop support for not following symlinks when expanding non-recursive pattern parts; it wasn't requested in the original issue, and it's a feature not found in any shells.This makes the API a easier to grok by eliminating `None` as an option.No news blurb as `follow_symlinks` was new in 3.13.
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
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.
Uh oh!
There was an error while loading.Please reload this page.
Replace tri-state
follow_symlinks
with booleanrecurse_symlinks
argument. The new argument controls whether symlinks are followed when expanding recursive**
wildcards. The possible argument values correspond as follows:We therefore drop support for not following symlinks when expanding non-recursive pattern parts; it wasn't requested in the original issue, and it's a feature not found in any shells.
This makes the API a easier to grok by eliminating
None
as an option.No news blurb as
follow_symlinks
was new in 3.13.📚 Documentation preview 📚:https://cpython-previews--117311.org.readthedocs.build/