1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
|
:mod:`importlib.resources` -- Package resource reading, opening and access
--------------------------------------------------------------------------
.. module:: importlib.resources
:synopsis: Package resource reading, opening, and access
**Source code:** :source:`Lib/importlib/resources/__init__.py`
--------------
.. versionadded:: 3.7
This module leverages Python's import system to provide access to *resources*
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.
Resources can be opened or read in either binary or text mode.
Resources are roughly akin to files inside directories, though it's important
to keep in mind that this is just a metaphor. Resources and packages **do
not** have to exist as physical files and directories on the file system:
for example, a package and its resources can be imported from a zip file using
:py:mod:`zipimport`.
.. note::
This module provides functionality similar to `pkg_resources
<https://setuptools.readthedocs.io/en/latest/pkg_resources.html>`_ `Basic
Resource Access
<https://setuptools.readthedocs.io/en/latest/pkg_resources.html#basic-resource-access>`_
without the performance overhead of that package. This makes reading
resources included in packages easier, with more stable and consistent
semantics.
The standalone backport of this module provides more information
on `using importlib.resources
<https://importlib-resources.readthedocs.io/en/latest/using.html>`_ and
`migrating from pkg_resources to importlib.resources
<https://importlib-resources.readthedocs.io/en/latest/migration.html>`_.
:class:`Loaders <importlib.abc.Loader>` that wish to support resource reading should implement a
``get_resource_reader(fullname)`` method as specified by
:class:`importlib.resources.abc.ResourceReader`.
.. class:: Anchor
Represents an anchor for resources, either a :class:`module object
<types.ModuleType>` or a module name as a string. Defined as
``Union[str, ModuleType]``.
.. function:: files(anchor: Optional[Anchor] = None)
Returns a :class:`~importlib.resources.abc.Traversable` object
representing the resource container (think directory) and its resources
(think files). A Traversable may contain other containers (think
subdirectories).
*anchor* is an optional :class:`Anchor`. If the anchor is a
package, resources are resolved from that package. If a module,
resources are resolved adjacent to that module (in the same package
or the package root). If the anchor is omitted, the caller's module
is used.
.. versionadded:: 3.9
.. versionchanged:: 3.12
*package* parameter was renamed to *anchor*. *anchor* can now
be a non-package module and if omitted will default to the caller's
module. *package* is still accepted for compatibility but will raise
a :exc:`DeprecationWarning`. Consider passing the anchor positionally or
using ``importlib_resources >= 5.10`` for a compatible interface
on older Pythons.
.. function:: as_file(traversable)
Given a :class:`~importlib.resources.abc.Traversable` object representing
a file or directory, typically from :func:`importlib.resources.files`,
return a context manager for use in a :keyword:`with` statement.
The context manager provides a :class:`pathlib.Path` object.
Exiting the context manager cleans up any temporary file or directory
created when the resource was extracted from e.g. a zip file.
Use ``as_file`` when the Traversable methods
(``read_text``, etc) are insufficient and an actual file or directory on
the file system is required.
.. versionadded:: 3.9
.. versionchanged:: 3.12
Added support for *traversable* representing a directory.
.. _importlib_resources_functional:
Functional API
^^^^^^^^^^^^^^
A set of simplified, backwards-compatible helpers is available.
These allow common operations in a single function call.
For all the following functions:
- *anchor* is an :class:`~importlib.resources.Anchor`,
as in :func:`~importlib.resources.files`.
Unlike in ``files``, it may not be omitted.
- *path_names* are components of a resource's path name, relative to
the anchor.
For example, to get the text of resource named ``info.txt``, use::
importlib.resources.read_text(my_module, "info.txt")
Like :meth:`Traversable.joinpath <importlib.resources.abc.Traversable>`,
The individual components should use forward slashes (``/``)
as path separators.
For example, the following are equivalent::
importlib.resources.read_binary(my_module, "pics/painting.png")
importlib.resources.read_binary(my_module, "pics", "painting.png")
For backward compatibility reasons, functions that read text require
an explicit *encoding* argument if multiple *path_names* are given.
For example, to get the text of ``info/chapter1.txt``, use::
importlib.resources.read_text(my_module, "info", "chapter1.txt",
encoding='utf-8')
.. function:: open_binary(anchor, *path_names)
Open the named resource for binary reading.
See :ref:`the introduction <importlib_resources_functional>` for
details on *anchor* and *path_names*.
This function returns a :class:`~typing.BinaryIO` object,
that is, a binary stream open for reading.
This function is roughly equivalent to::
files(anchor).joinpath(*path_names).open('rb')
.. versionchanged:: 3.13
Multiple *path_names* are accepted.
.. function:: open_text(anchor, *path_names, encoding='utf-8', errors='strict')
Open the named resource for text reading.
By default, the contents are read as strict UTF-8.
See :ref:`the introduction <importlib_resources_functional>` for
details on *anchor* and *path_names*.
*encoding* and *errors* have the same meaning as in built-in :func:`open`.
For backward compatibility reasons, the *encoding* argument must be given
explicitly if there are multiple *path_names*.
This limitation is scheduled to be removed in Python 3.15.
This function returns a :class:`~typing.TextIO` object,
that is, a text stream open for reading.
This function is roughly equivalent to::
files(anchor).joinpath(*path_names).open('r', encoding=encoding)
.. versionchanged:: 3.13
Multiple *path_names* are accepted.
*encoding* and *errors* must be given as keyword arguments.
.. function:: read_binary(anchor, *path_names)
Read and return the contents of the named resource as :class:`bytes`.
See :ref:`the introduction <importlib_resources_functional>` for
details on *anchor* and *path_names*.
This function is roughly equivalent to::
files(anchor).joinpath(*path_names).read_bytes()
.. versionchanged:: 3.13
Multiple *path_names* are accepted.
.. function:: read_text(anchor, *path_names, encoding='utf-8', errors='strict')
Read and return the contents of the named resource as :class:`str`.
By default, the contents are read as strict UTF-8.
See :ref:`the introduction <importlib_resources_functional>` for
details on *anchor* and *path_names*.
*encoding* and *errors* have the same meaning as in built-in :func:`open`.
For backward compatibility reasons, the *encoding* argument must be given
explicitly if there are multiple *path_names*.
This limitation is scheduled to be removed in Python 3.15.
This function is roughly equivalent to::
files(anchor).joinpath(*path_names).read_text(encoding=encoding)
.. versionchanged:: 3.13
Multiple *path_names* are accepted.
*encoding* and *errors* must be given as keyword arguments.
.. function:: path(anchor, *path_names)
Provides the path to the *resource* as an actual file system path. This
function returns a context manager for use in a :keyword:`with` statement.
The context manager provides a :class:`pathlib.Path` object.
Exiting the context manager cleans up any temporary files created, e.g.
when the resource needs to be extracted from a zip file.
For example, the :meth:`~pathlib.Path.stat` method requires
an actual file system path; it can be used like this::
with importlib.resources.path(anchor, "resource.txt") as fspath:
result = fspath.stat()
See :ref:`the introduction <importlib_resources_functional>` for
details on *anchor* and *path_names*.
This function is roughly equivalent to::
as_file(files(anchor).joinpath(*path_names))
.. versionchanged:: 3.13
Multiple *path_names* are accepted.
*encoding* and *errors* must be given as keyword arguments.
.. function:: is_resource(anchor, *path_names)
Return ``True`` if the named resource exists, otherwise ``False``.
This function does not consider directories to be resources.
See :ref:`the introduction <importlib_resources_functional>` for
details on *anchor* and *path_names*.
This function is roughly equivalent to::
files(anchor).joinpath(*path_names).is_file()
.. versionchanged:: 3.13
Multiple *path_names* are accepted.
.. function:: contents(anchor, *path_names)
Return an iterable over the named items within the package or path.
The iterable returns names of resources (e.g. files) and non-resources
(e.g. directories) as :class:`str`.
The iterable does not recurse into subdirectories.
See :ref:`the introduction <importlib_resources_functional>` for
details on *anchor* and *path_names*.
This function is roughly equivalent to::
for resource in files(anchor).joinpath(*path_names).iterdir():
yield resource.name
.. deprecated:: 3.11
Prefer ``iterdir()`` as above, which offers more control over the
results and richer functionality.
|