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 jaraco
Recipients jaraco
Date 2021-12-17.21:37:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1639777039.87.0.134245043353.issue46118@roundup.psfhosted.org>
In-reply-to
Content
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`.
History
Date User Action Args
2021-12-17 21:37:19jaracosetrecipients: + jaraco
2021-12-17 21:37:19jaracosetmessageid: <1639777039.87.0.134245043353.issue46118@roundup.psfhosted.org>
2021-12-17 21:37:19jaracolinkissue46118 messages
2021-12-17 21:37:19jaracocreate