# Deprecating importlib.resources legacy API

**URL:** <https://discuss.python.org/t/deprecating-importlib-resources-legacy-api/11386>\
**Category:** Core Development\
**Created:** [October 21, 2021, 3:34pm UTC](https://discuss.python.org/t/deprecating-importlib-resources-legacy-api/11386 "2021-10-21T15:34:52Z")\
**Posts on this page:** 1\
**Showing post:** 29

<div class="post-metadata">

**Author:** ![encukou](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/encukou/32/2461_2.png) [@encukou](https://discuss.python.org/u/encukou)\
**Post date:** [January 16, 2024, 10:23am UTC](https://discuss.python.org/t/deprecating-importlib-resources-legacy-api/11386/29 "2024-01-16T10:23:01Z")

</div>

> [@jaraco](#):
>
> If someone volunteers to carry the maintenance burden of the legacy module (documentation, bug triage, tests, etc) and any divergence in CPython, I’ll allow that person to decide if and how to deprecate the module (including backing out the existing deprecation to a PendingDeprecationWarning or removing the warning completely).

Hello,  
I believe the removal hurts users (especially since the replacement is not available in still-supported 3.8). I don’t want people who are disillusioned by the complexity to go back to ` __file__ `.  
And now, I am now in a position where I can commit to supporting the functional API. So, I’d like to do that!  
What would be the best way to do so? Should I work in CPython, or send PRs to the external repo?

* * *

FWIW, I find the functional API to be much friendlier that `Traversable`. I’d like to explore keeping it long-term, leaving `Traversable` targetted more for people who need to subclass it. I believe I can get rid of the drawback of not supporting directories.

---

_[View the full topic](https://discuss.python.org/t/deprecating-importlib-resources-legacy-api/11386)._
