# Make pathlib extensible

**URL:** <https://discuss.python.org/t/make-pathlib-extensible/3428>\
**Category:** Ideas\
**Created:** [February 24, 2020, 12:15am UTC](https://discuss.python.org/t/make-pathlib-extensible/3428 "2020-02-24T00:15:07Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pitrou](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pitrou/32/28_2.png) [@pitrou](https://discuss.python.org/u/pitrou)\
**Post date:** [February 24, 2020, 9:14am UTC](https://discuss.python.org/t/make-pathlib-extensible/3428/2 "2020-02-24T09:14:09Z")

</div>

@barneygale That’s… interesting. 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.

It would be nice if you could directly modify `pathlib` and post the diff (or PR) somewhere. Some parts of `pathlib` use shortcurts for speed (especially `Path` construction), and I’m curious if you can retain the shortcuts while respecting the accessor abstraction.

---

_[View the full topic](https://discuss.python.org/t/make-pathlib-extensible/3428)._