Description
Bug report
Bug description:
Path.exists() and Path.resolve() do not work consistently with each other if the current working directory is deleted after Python is launched.
For example, if I open a Python 3.13.0 interpreter (although I have verified this occurs in older versions as well) in a directory, and then delete that directory I experience the following behavior:
>>> from pathlib import Path
>>> Path('.').exists()
True
>>> Path('.').resolve()
Traceback (most recent call last):
File "<python-input-2>", line 1, in <module>
Path('.').resolve()
~~~~~~~~~~~~~~~~~^^
File "/opt/homebrew/Caskroom/mambaforge/base/envs/py313minimal/lib/python3.13/pathlib/_local.py", line 670, in resolve
return self.with_segments(os.path.realpath(self, strict=strict))
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
File "<frozen posixpath>", line 413, in realpath
FileNotFoundError: [Errno 2] No such file or directoryNote how Path('.').exists() is True, even though the cwd does not exist, and then when I try to resolve the path, I get a FileNotFoundError.
You also get a FileNotFoundError when the cwd doesn't exist for all relative paths, even though in the non-dot cases Path.exists() works as one would expect.
>>> Path('asdf').exists()
False
>>> Path('asdf').resolve().exists()
Traceback (most recent call last):
File "<python-input-4>", line 1, in <module>
Path('asdf').resolve().exists()
~~~~~~~~~~~~~~~~~~~~^^
File "/opt/homebrew/Caskroom/mambaforge/base/envs/py313minimal/lib/python3.13/pathlib/_local.py", line 670, in resolve
return self.with_segments(os.path.realpath(self, strict=strict))
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
File "<frozen posixpath>", line 413, in realpath
FileNotFoundError: [Errno 2] No such file or directoryIf the cwd does exist, you can see that Path.resolve() does not raise a FileNotFoundError when the path does not exist.
>>> from pathlib import Path
>>> Path('asdf').exists()
False
>>> Path('asdf').resolve()
PosixPath('/Users/danielblanchard/asdf')I believe resolve is doing the right thing here, but two things are not working as expected when the cwd is deleted:
Path('.').exists()andPath('').exists()should not tell you a path exists that doesn't.Path('foo').resolve()should not raise aFileNotFoundErrorif the cwd doesn't exist, unlessstrict=True. Instead it should just return the initial path.
CPython versions tested on:
3.9, 3.12, 3.13
Operating systems tested on:
Linux, macOS