8000 Cleanup Sphinx lint errors · python/cpython@9ba869b · GitHub
[go: up one dir, main page]

Skip to content

Commit 9ba869b

Browse files
committed
Cleanup Sphinx lint errors
1 parent fa4172b commit 9ba869b

File tree

3 files changed

+12
-11
lines changed

3 files changed

+12
-11
lines changed

Doc/library/functions.rst

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1063,14 +1063,15 @@ are always available. They are listed here in alphabetical order.
10631063
variable names as the keys, and their currently bound references as the
10641064
values.
10651065

1066-
At module scope, as well as when using ``exec()`` or ``eval()`` with a
1067-
single namespace, this function returns the same namespace as ``globals()``.
1066+
At module scope, as well as when using :func:`exec` or :func:`eval` with
1067+
a single namespace, this function returns the same namespace as
1068+
:func:`globals`.
10681069

10691070
At class scope, it returns the namespace that will be passed to the
10701071
metaclass constructor.
10711072

10721073
When using ``exec()`` or ``eval()`` with separate local and global
1073-
namespaces, it returns the local namespace passed in to the function call.
1074+
arguments, it returns the local namespace passed in to the function call.
10741075

10751076
In all of the above cases, each call to ``locals()`` in a given frame of
10761077
execution will return the *same* mapping object. Changes made through
@@ -1116,20 +1117,20 @@ are always available. They are listed here in alphabetical order.
11161117
returned dictionary with the results of subsequent calls to ``locals()``.
11171118

11181119
.. versionchanged:: 3.13
1119-
As part of :pep:`667`, calling `locals()` in a comprehension at module
1120-
or class scope (including via `exec` or `eval`) once more behaves as if
1120+
As part of :pep:`667`, calling ``locals()`` in a comprehension at module
1121+
or class scope (including via ``exec`` or ``eval``) once more behaves as if
11211122
the comprehension were running as an independent nested function (i.e.
11221123
the local variables from the containing scope are not included).
11231124

11241125
.. versionchanged:: 3.12
1125-
As part of :pep:`709`, calling `locals()` in a comprehension at module
1126-
or class scope (including via `exec` or `eval`) produces an independent
1126+
As part of :pep:`709`, calling ``locals()`` in a comprehension at module
1127+
or class scope (including via ``exec`` or ``eval``) produces an independent
11271128
snapshot of the containing scope with the comprehension iteration
11281129
variable(s) included.
11291130

11301131
.. versionchanged:: 3.12
1131-
As part of :pep:`709`, calling `locals()` in a comprehension as part of a
1132-
function, generator, or coroutine returns the same `locals()` reference
1132+
As part of :pep:`709`, calling ``locals()`` in a comprehension as part of a
1133+
function, generator, or coroutine returns the same ``locals()`` reference
11331134
as calls in the containing scope.
11341135

11351136
..

Doc/library/pdb.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ The typical usage to inspect a crashed program is::
124124
(Pdb)
125125

126126
.. versionchanged:: 3.13
127-
The implementation of :pep:`667` means that name assignments made via `pdb`
127+
The implementation of :pep:`667` means that name assignments made via ``pdb``
128128
will consistently and directly affect the active scope, even when running
129129
inside a function, generator, or coroutine.
130130

Doc/whatsnew/3.13.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ Interpreter improvements:
9494
Performance improvements are modest -- we expect to be improving this
9595
over the next few releases.
9696

97-
* :pep:`667`: The `func:`locals` builtin now has defined semantics when mutating
97+
* :pep:`667`: The :func:`locals` builtin now has defined semantics when mutating
9898
the returned mapping. Python debuggers and similar tools may now more reliably
9999
update local variables in optimised frames even during concurrent code
100100
execution.

0 commit comments

Comments
 (0)
0