gh-140971: Doc: Clarify pathlib.Path("") behavior - #140993
Closed
LiuQhahah wants to merge 1 commit into
Closed
Conversation
|
All commit authors signed the Contributor License Agreement. |
terryjreedy
reviewed
Nov 4, 2025
|
This PR is stale because it has been open for 30 days with no activity. |
Member
|
I'm sorry but I am closing as Terry's changes haven't been made in several months. |
Member
|
If you approve of my suggestion, I will make the change and merge. |
Member
|
It looks good to me, please ping when you open a PR and I can approve. |
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
4 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.
Fixes #140971
This PR clarifies the behavior of
pathlib.Path("")in the documentation.The current behavior, where
pathlib.Path("").exists()returnsTrue, is intentional butcan be confusing because it differs from
os.path.exists(""), which returnsFalse.This change adds a note to the
PurePathconstructor documentation to explain that an empty string path segment refers to the current directory. This makes the behavior explicit to users and helps prevent further confusion.📚 Documentation preview 📚: https://cpython-previews--140993.org.readthedocs.build/