This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author barneygale
Recipients barneygale
Date 2021-04-07.02:32:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1617762768.57.0.0406169855145.issue43757@roundup.psfhosted.org>
In-reply-to
Content
Under-the-hood functionality in pathlib is divided between:

- The 'flavour', which implements path syntax (separators, casefolding, etc)
- The 'accessor', which accesses the local (file)system.

The '_WindowsFlavour/_PosixFlavour.resolve()' function is misplaced, as it requires OS calls such as `os.getcwd()`, `os.readlink()`, and `nt._getfinalpathname()`. While the implementation *does* differ across Windows and POSIX, it's still properly part of the accessor interface, and not the flavour interface.

In preparation for addressing bpo-24132 I'd like to get these interfaces really tidy. Once bpo-39899 is fixed, this will be the last remaining flavour method that does accessor-y things.
History
Date User Action Args
2021-04-07 02:32:48barneygalesetrecipients: + barneygale
2021-04-07 02:32:48barneygalesetmessageid: <1617762768.57.0.0406169855145.issue43757@roundup.psfhosted.org>
2021-04-07 02:32:48barneygalelinkissue43757 messages
2021-04-07 02:32:47barneygalecreate