-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
GH-99334: Explain that PurePath.is_relative_to()
is purely lexical.
#114031
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
Conversation
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.
Perhaps you could add a note that users may wish to only call it with resolved / normalised / casefolded / etc paths, and provide a brief sketch of doing so?
Thanks for the review!
It's hard to give good advice, because there are several edge cases that may or may not be relevant depending on user need. (tbh I'd rather |
I think the actual change here is fine to merge -- the comment was just the cherry on top, but it would simply add confusion then best avoided -- and the reader can infer that no path processing is done from the current text as proposed. A |
Thanks again! |
Thanks @barneygale for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
…xical. (pythonGH-114031) (cherry picked from commit 3a61d24) Co-authored-by: Barney Gale <barney.gale@gmail.com>
Sorry, @barneygale, I could not cleanly backport this to
|
GH-114460 is a backport of this pull request to the 3.12 branch. |
…xical. (python#114031) (cherry picked from commit 3a61d24)
…rely lexical. (pythonGH-114031). (cherry picked from commit 3a61d24) Co-authored-by: Barney Gale <barney.gale@gmail.com>
GH-114461 is a backport of this pull request to the 3.11 branch. |
📚 Documentation preview 📚: https://cpython-previews--114031.org.readthedocs.build/