Skip to content

Commit 39e6b40

Browse files
committed
Suppress heading xrefs
1 parent 5d4a45d commit 39e6b40

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

peps/pep-0810.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1016,8 +1016,8 @@ Yes, accessing a module's ``__dict__`` will reify all lazy objects in that
10161016
module. Individual lazy objects can be resolved by calling their ``get()``
10171017
method.
10181018

1019-
What's the difference between :func:`globals` and ``mod.__dict__`` for lazy imports?
1020-
------------------------------------------------------------------------------------
1019+
What's the difference between ``globals()`` and ``mod.__dict__`` for lazy imports?
1020+
----------------------------------------------------------------------------------
10211021

10221022
Calling ``globals()`` returns the module's dictionary without reifying lazy
10231023
imports -- you'll see lazy proxy objects when accessing them through the
@@ -1149,8 +1149,8 @@ also be loaded if the user uses ``annotationlib.get_annotations()`` or
11491149
pass
11501150
print(foo.__annotations__) # Triggers loading the fake_typing module
11511151
1152-
How do lazy imports interact with :func:`dir`, :func:`getattr`, and module introspection?
1153-
-----------------------------------------------------------------------------------------
1152+
How do lazy imports interact with ``dir()``, ``getattr()``, and module introspection?
1153+
-------------------------------------------------------------------------------------
11541154

11551155
Accessing lazy imports through normal attribute access or ``getattr()``
11561156
will trigger reification. Calling ``dir()`` on a module will reify all lazy
@@ -1265,8 +1265,8 @@ You can observe the specialization using ``dis.dis(use_json, adaptive=True)``:
12651265
The specialized ``LOAD_GLOBAL_MODULE`` and ``LOAD_ATTR_MODULE`` instructions
12661266
are optimized fast paths with no overhead for checking lazy imports.
12671267

1268-
What about :data:`sys.modules`? When does a lazy import appear there?
1269-
---------------------------------------------------------------------
1268+
What about ``sys.modules``? When does a lazy import appear there?
1269+
-----------------------------------------------------------------
12701270

12711271
A lazily imported module does **not** appear in ``sys.modules`` until it's
12721272
reified (first used). Once reified, it appears in ``sys.modules`` just like

0 commit comments

Comments
 (0)