Skip to content

PEP 810: rename get() to resolve() #4653

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 10, 2025
Merged

PEP 810: rename get() to resolve() #4653

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions peps/pep-0810.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -368,7 +368,7 @@ Lazy modules, as well as names lazy imported from modules, are represented
by :class:`!types.LazyImportType` instances, which are resolved to the real
object (reified) before they can be used. This reification is usually done
automatically (see below), but can also be done by calling the lazy object's
``get`` method.
``resolve`` method.

Lazy import mechanism
---------------------
Expand Down Expand Up @@ -493,8 +493,8 @@ Example using ``__dict__`` from external code:
However, calling ``globals()`` does **not** trigger reification -- it returns
the module's dictionary, and accessing lazy objects through that dictionary
still returns lazy proxy objects that need to be manually reified upon use. A
lazy object can be resolved explicitly by calling the ``get`` method. Other,
more indirect ways of accessing arbitrary globals (e.g. inspecting
lazy object can be resolved explicitly by calling the ``resolve`` method.
Other, more indirect ways of accessing arbitrary globals (e.g. inspecting
``frame.f_globals``) also do **not** reify all the objects.

Example using ``globals()``:
Expand All @@ -510,8 +510,8 @@ Example using ``globals()``:
print('json' in sys.modules) # False - still lazy
print(type(g['json'])) # <class 'LazyImport'>

# Explicitly reify using the get() method
resolved = g['json'].get()
# Explicitly reify using the resolve() method
resolved = g['json'].resolve()

print(type(resolved)) # <class 'module'>
print('json' in sys.modules) # True - now loaded
Expand Down Expand Up @@ -1252,7 +1252,7 @@ Can I force reification of a lazy import without using it?
----------------------------------------------------------

Yes, accessing a module's ``__dict__`` will reify all lazy objects in that
module. Individual lazy objects can be resolved by calling their ``get()``
module. Individual lazy objects can be resolved by calling their ``resolve()``
method.

What's the difference between ``globals()`` and ``mod.__dict__`` for lazy imports?
Expand Down