From: Petr Viktorin Date: Wed, 23 Jul 2025 12:01:38 +0000 (+0200) Subject: gh-136516: Mention installation artifacts as de-facto resources (GH-136419) X-Git-Tag: v3.15.0a1~871 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=fac4964fdb2ae12969b485de496dd6d064fdbe99;p=thirdparty%2FPython%2Fcpython.git gh-136516: Mention installation artifacts as de-facto resources (GH-136419) Files like NUL on windows are, from `importlib.resources` point of view, an artifact caused by installing to a filesystem directory. Mention these. --- diff --git a/Doc/library/importlib.resources.rst b/Doc/library/importlib.resources.rst index e002198899c8..7a11f4fe0690 100644 --- a/Doc/library/importlib.resources.rst +++ b/Doc/library/importlib.resources.rst @@ -16,11 +16,12 @@ within *packages*. "Resources" are file-like resources associated with a module or package in Python. The resources may be contained directly in a package, within a subdirectory contained in that package, or adjacent to modules outside a -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. +package. Resources may be text or binary. As a result, a package's Python +module sources (.py), compilation artifacts (pycache), and installation +artifacts (like :func:`reserved filenames ` +in directories) are technically de-facto resources of that package. +In practice, however, resources are primarily those non-Python artifacts +exposed specifically by the package author. Resources can be opened or read in either binary or text mode.