Deprecating importlib.resources legacy API

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.

7 Likes