[issue39659] pathlib calls `os.getcwd()` without using accessor

Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ P

[issue39659] pathlib calls `os.getcwd()` without using accessor

Steve Dower added the comment: New changeset b05440c52b9814dbd47f679d47367e87855bd7b5 by Barney Gale in branch 'master': bpo-39659: Route calls from pathlib.Path to os.getcwd() via the path accessor (GH-18834) https://github.com/python/cpython/commit/b05440c52b9814dbd47f679d47367e87855bd7b5

[issue39659] pathlib calls `os.getcwd()` without using accessor

Change by Karthikeyan Singaravelan : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue39659] pathlib calls `os.getcwd()` without using accessor

Change by Barney Gale : -- keywords: +patch pull_requests: +18191 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18834 ___ Python tracker ___

[issue39659] pathlib calls `os.getcwd()` without using accessor

Barney Gale added the comment: Those methods are non-pure, i.e. part of `Path` but not `PurePath`. Only impure paths have accessors. The `_Accessor` docstring says: "an accessor implements a particular (system-specific or not) way of accessing paths on the filesystem". This abstraction is pr

[issue39659] pathlib calls `os.getcwd()` without using accessor

Emmanuel Arias added the comment: Sorry, I cannot catch what is the problem of not use _Accesor on PurePath class -- nosy: +eamanu ___ Python tracker ___ _

[issue39659] pathlib calls `os.getcwd()` without using accessor

New submission from Barney Gale : Whereas most calls to `os` functions from `pathlib.Path` methods happen via `pathlib._Accessor` methods, retrieving the current working directory does not. This problem occurs when calling the `pathlib.Path.cwd()`, `~resolve()` and `~absolute()` methods. ---