unexpected behavior of pathlib with empty string
Open
Nobody has claimed this yet.
docs
topic-pathlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Bug report
Bug description:
While os.path.exists("") correctly returns False, the same input with Path("").exists() returns True.
>>> from pathlib import Path
>>> import os
>>> Path("").exists()
True
>>> os.path.exists("")
False
>>>
CPython versions tested on:
3.13
Operating systems tested on:
Linux
Linked PRs
- gh-140993
- gh-157293
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the pathlib and os.path.exists examples on Python 3.13/Linux, then inspect pathlib's empty-path handling and its related tests. Review linked PRs gh-140993 and gh-157293 before starting; done means the discrepancy has a confirmed expected behavior and corresponding regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100