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 FFY00, docs@python, jaraco
Date 2021-05-23.18:56:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1621796195.44.0.605722637602.issue44164@roundup.psfhosted.org>
In-reply-to
Content
I've not previously seen a definition of resources. The original implementation of importlib_resources excluded 'directories' as resources and excluded support for resources being in subdirectories (only files in packages were allowed). Now resources can be found in subdirectories that are not packages and in namesepace packages. I'd describe resources thus:

"Resources" are file-like resources associated with a module[1] or package in Python. The resources may be contained directly in a package or within a subdirectory contained in that package. Resources may be text or binary. As a result, Python module sources (.py) of a package and compilation artifacts (__pycache__) are technically de-facto resources of that package. In practice, however, resources are primarily those non-Python artifacts exposed specifically by the package author.


[1] Resources associated with top-level modules are not yet supported by importlib[._]resources (https://github.com/python/importlib_resources/issues/203) but were supported by pkg_resources.
History
Date User Action Args
2021-05-23 18:56:35jaracosetrecipients: + jaraco, docs@python, FFY00
2021-05-23 18:56:35jaracosetmessageid: <1621796195.44.0.605722637602.issue44164@roundup.psfhosted.org>
2021-05-23 18:56:35jaracolinkissue44164 messages
2021-05-23 18:56:35jaracocreate