Jason R. Coombs <jar...@jaraco.com> added the comment:
Compatibility considerations:
- importlib.readers and importlib.simple are public, so probably need aliases.
- Same abc classes.
Should we embark on an effort to migrate users to the new names in
`importlib.resources`, or simply leave the `importlib.{mod}` names as
preferred? My instinct is to do the former, mainly because then the names would
be congruent between `importlib.resources` and `importlib_resources`. But I'm
also reluctant to introduce a deprecation (even deferred) comparable to what
happened with `collections.abc`.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue46118>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
