GH-82805: Fix handling of single-dot file extensions in pathlib #118952
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.
pathlib now treats "
.
" as a valid file extension (suffix). This brings it in line withos.path.splitext()
.In the (private) pathlib ABCs, we add a new
ParserBase.splitext()
method that splits a path into a(root, ext)
pair, likeos.path.splitext()
. This method is called byPurePathBase.stem
,suffix
, etc. In a future version of pathlib, we might make these base classes public, and so users will be able to define their ownsplitext()
method to control file extension splitting.In
pathlib.PurePath
we add optimisedstem
,suffix
andsuffixes
properties that don't usesplitext()
, which avoids computing the path base name twice.馃摎 Documentation preview 馃摎: https://cpython-previews--118952.org.readthedocs.build/