gh-140971: Doc: Clarify pathlib.Path("") behavior #140993
Open
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/