mirror of
https://github.com/python/cpython.git
synced 2025-12-15 21:44:50 +00:00
#5341: more built-in vs builtin fixes.
This commit is contained in:
parent
c02bbe328d
commit
21e99f4924
7 changed files with 62 additions and 62 deletions
|
|
@ -119,7 +119,7 @@ searched. The global statement must precede all uses of the name.
|
|||
|
||||
.. index:: pair: restricted; execution
|
||||
|
||||
The built-in namespace associated with the execution of a code block is actually
|
||||
The builtins namespace associated with the execution of a code block is actually
|
||||
found by looking up the name ``__builtins__`` in its global namespace; this
|
||||
should be a dictionary or a module (in the latter case the module's dictionary
|
||||
is used). By default, when in the :mod:`__main__` module, ``__builtins__`` is
|
||||
|
|
@ -131,7 +131,7 @@ weak form of restricted execution.
|
|||
.. impl-detail::
|
||||
|
||||
Users should not touch ``__builtins__``; it is strictly an implementation
|
||||
detail. Users wanting to override values in the built-in namespace should
|
||||
detail. Users wanting to override values in the builtins namespace should
|
||||
:keyword:`import` the :mod:`__builtin__` (no 's') module and modify its
|
||||
attributes appropriately.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue