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-01-23.18:15:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1611425755.47.0.494853383169.issue43012@roundup.psfhosted.org>
In-reply-to
Content
Per Pitrou:

> The original intent for the “accessor” thing was to have a variant that did all accesses under a filesystem tree in a race condition-free way using openat and friends. It turned out to be much too hairy to actually implement, so was entirely abandoned, but the accessor abstraction was left there.

https://discuss.python.org/t/make-pathlib-extensible/3428/2

Accessors are:

- Lacking any internal purpose - '_NormalAccessor' is the only implementation
- Lacking any firm conceptual difference to `Path` objects themselves (inc. subclasses)
- Non-public, i.e. underscore prefixed - '_Accessor' and '_NormalAccessor' 
- Unofficially used to implement customized `Path` objects, but once once bpo-24132 lands there will be a supported route for that.

When bpo-24132 lands, I think we're free to remove accessors and simplify some code
History
Date User Action Args
2021-01-23 18:15:55barneygalesetrecipients: + barneygale
2021-01-23 18:15:55barneygalesetmessageid: <1611425755.47.0.494853383169.issue43012@roundup.psfhosted.org>
2021-01-23 18:15:55barneygalelinkissue43012 messages
2021-01-23 18:15:55barneygalecreate