➜

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.20:54:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1639774468.14.0.755654670872.issue46118@roundup.psfhosted.org>
In-reply-to
Content
The importlib.resources module has several modules on which it relies (_adapters, _legacy, simple) and some classes in other modules shared by other parts of importlib (namely abc).

Because these implementations overlap, it adds difficulty in maintaining the `importlib_resources` backport, which must maintain these modules but keep them separate from the unrelated functionality in other parts of importlib.

In an earlier refactoring, `importlib.metadata` was refactored into its own package (https://github.com/python/cpython/pull/25565). This refactoring had benefits of making it clearer which functionality of importlib was related to metadata and which was not.

I'd like to do the same for importlib.resources.

The main complicate
History
Date User Action Args
2021-12-17 20:54:28jaracosetrecipients: + jaraco
2021-12-17 20:54:28jaracosetmessageid: <1639774468.14.0.755654670872.issue46118@roundup.psfhosted.org>
2021-12-17 20:54:28jaracolinkissue46118 messages
2021-12-17 20:54:28jaracocreate