mirror of
https://github.com/python/cpython.git
synced 2025-07-24 11:44:31 +00:00
GH-97950: Use new-style index directive ('module') (#103996)
* Use new-style index directive ('module') - C API * Use new-style index directive ('module') - Library * Use new-style index directive ('module') - Reference * Use new-style index directive ('module') - Tutorial * Uncomment module removal in pairindextypes * Use new-style index directive ('module') - C API * Use new-style index directive ('module') - Library * Use new-style index directive ('module') - Reference
This commit is contained in:
parent
cd9a56c2b0
commit
d0122372f2
33 changed files with 65 additions and 69 deletions
|
@ -602,7 +602,7 @@ Signal Handling
|
||||||
.. c:function:: int PyErr_CheckSignals()
|
.. c:function:: int PyErr_CheckSignals()
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
module: signal
|
pair: module; signal
|
||||||
single: SIGINT
|
single: SIGINT
|
||||||
single: KeyboardInterrupt (built-in exception)
|
single: KeyboardInterrupt (built-in exception)
|
||||||
|
|
||||||
|
@ -633,7 +633,7 @@ Signal Handling
|
||||||
.. c:function:: void PyErr_SetInterrupt()
|
.. c:function:: void PyErr_SetInterrupt()
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
module: signal
|
pair: module; signal
|
||||||
single: SIGINT
|
single: SIGINT
|
||||||
single: KeyboardInterrupt (built-in exception)
|
single: KeyboardInterrupt (built-in exception)
|
||||||
|
|
||||||
|
@ -648,7 +648,7 @@ Signal Handling
|
||||||
.. c:function:: int PyErr_SetInterruptEx(int signum)
|
.. c:function:: int PyErr_SetInterruptEx(int signum)
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
module: signal
|
pair: module; signal
|
||||||
single: KeyboardInterrupt (built-in exception)
|
single: KeyboardInterrupt (built-in exception)
|
||||||
|
|
||||||
Simulate the effect of a signal arriving. The next time
|
Simulate the effect of a signal arriving. The next time
|
||||||
|
|
|
@ -336,9 +336,9 @@ Initializing and finalizing the interpreter
|
||||||
single: PyEval_InitThreads()
|
single: PyEval_InitThreads()
|
||||||
single: modules (in module sys)
|
single: modules (in module sys)
|
||||||
single: path (in module sys)
|
single: path (in module sys)
|
||||||
module: builtins
|
pair: module; builtins
|
||||||
module: __main__
|
pair: module; __main__
|
||||||
module: sys
|
pair: module; sys
|
||||||
triple: module; search; path
|
triple: module; search; path
|
||||||
single: PySys_SetArgv()
|
single: PySys_SetArgv()
|
||||||
single: PySys_SetArgvEx()
|
single: PySys_SetArgvEx()
|
||||||
|
@ -1051,7 +1051,7 @@ code, or when embedding the Python interpreter:
|
||||||
|
|
||||||
.. deprecated:: 3.9
|
.. deprecated:: 3.9
|
||||||
|
|
||||||
.. index:: module: _thread
|
.. index:: pair: module; _thread
|
||||||
|
|
||||||
|
|
||||||
.. c:function:: int PyEval_ThreadsInitialized()
|
.. c:function:: int PyEval_ThreadsInitialized()
|
||||||
|
@ -1494,9 +1494,9 @@ function. You can create and destroy them using the following functions:
|
||||||
.. c:function:: PyThreadState* Py_NewInterpreter()
|
.. c:function:: PyThreadState* Py_NewInterpreter()
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
module: builtins
|
pair: module; builtins
|
||||||
module: __main__
|
pair: module; __main__
|
||||||
module: sys
|
pair: module; sys
|
||||||
single: stdout (in module sys)
|
single: stdout (in module sys)
|
||||||
single: stderr (in module sys)
|
single: stderr (in module sys)
|
||||||
single: stdin (in module sys)
|
single: stdin (in module sys)
|
||||||
|
|
|
@ -705,9 +705,9 @@ interpreter can only be used after the interpreter has been initialized.
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
single: Py_Initialize()
|
single: Py_Initialize()
|
||||||
module: builtins
|
pair: module; builtins
|
||||||
module: __main__
|
pair: module; __main__
|
||||||
module: sys
|
pair: module; sys
|
||||||
triple: module; search; path
|
triple: module; search; path
|
||||||
single: path (in module sys)
|
single: path (in module sys)
|
||||||
|
|
||||||
|
|
|
@ -208,7 +208,7 @@ In addition to these methods, lock objects can also be used via the
|
||||||
|
|
||||||
**Caveats:**
|
**Caveats:**
|
||||||
|
|
||||||
.. index:: module: signal
|
.. index:: pair: module; signal
|
||||||
|
|
||||||
* Threads interact strangely with interrupts: the :exc:`KeyboardInterrupt`
|
* Threads interact strangely with interrupts: the :exc:`KeyboardInterrupt`
|
||||||
exception will be received by an arbitrary thread. (When the :mod:`signal`
|
exception will be received by an arbitrary thread. (When the :mod:`signal`
|
||||||
|
|
|
@ -6,8 +6,8 @@
|
||||||
representations.
|
representations.
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
module: uu
|
pair: module; uu
|
||||||
module: base64
|
pair: module; base64
|
||||||
|
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
|
|
|
@ -301,7 +301,7 @@ Constants
|
||||||
.. versionadded:: 3.6
|
.. versionadded:: 3.6
|
||||||
|
|
||||||
|
|
||||||
.. index:: module: math
|
.. index:: pair: module; math
|
||||||
|
|
||||||
Note that the selection of functions is similar, but not identical, to that in
|
Note that the selection of functions is similar, but not identical, to that in
|
||||||
module :mod:`math`. The reason for having two modules is that some users aren't
|
module :mod:`math`. The reason for having two modules is that some users aren't
|
||||||
|
|
|
@ -68,7 +68,7 @@ Shallow copies of dictionaries can be made using :meth:`dict.copy`, and
|
||||||
of lists by assigning a slice of the entire list, for example,
|
of lists by assigning a slice of the entire list, for example,
|
||||||
``copied_list = original_list[:]``.
|
``copied_list = original_list[:]``.
|
||||||
|
|
||||||
.. index:: module: pickle
|
.. index:: pair: module; pickle
|
||||||
|
|
||||||
Classes can use the same interfaces to control copying that they use to control
|
Classes can use the same interfaces to control copying that they use to control
|
||||||
pickling. See the description of module :mod:`pickle` for information on these
|
pickling. See the description of module :mod:`pickle` for information on these
|
||||||
|
|
|
@ -7,8 +7,8 @@
|
||||||
**Source code:** :source:`Lib/copyreg.py`
|
**Source code:** :source:`Lib/copyreg.py`
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
module: pickle
|
pair: module; pickle
|
||||||
module: copy
|
pair: module; copy
|
||||||
|
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
|
|
|
@ -318,7 +318,7 @@ The following exceptions are the exceptions that are usually raised.
|
||||||
.. exception:: OSError([arg])
|
.. exception:: OSError([arg])
|
||||||
OSError(errno, strerror[, filename[, winerror[, filename2]]])
|
OSError(errno, strerror[, filename[, winerror[, filename2]]])
|
||||||
|
|
||||||
.. index:: module: errno
|
.. index:: pair: module; errno
|
||||||
|
|
||||||
This exception is raised when a system function returns a system-related
|
This exception is raised when a system function returns a system-related
|
||||||
error, including I/O failures such as "file not found" or "disk full"
|
error, including I/O failures such as "file not found" or "disk full"
|
||||||
|
|
|
@ -8,7 +8,7 @@
|
||||||
|
|
||||||
.. index:: single: filenames; wildcard expansion
|
.. index:: single: filenames; wildcard expansion
|
||||||
|
|
||||||
.. index:: module: re
|
.. index:: pair: module; re
|
||||||
|
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
|
@ -38,7 +38,7 @@ special characters used in shell-style wildcards are:
|
||||||
For a literal match, wrap the meta-characters in brackets.
|
For a literal match, wrap the meta-characters in brackets.
|
||||||
For example, ``'[?]'`` matches the character ``'?'``.
|
For example, ``'[?]'`` matches the character ``'?'``.
|
||||||
|
|
||||||
.. index:: module: glob
|
.. index:: pair: module; glob
|
||||||
|
|
||||||
Note that the filename separator (``'/'`` on Unix) is *not* special to this
|
Note that the filename separator (``'/'`` on Unix) is *not* special to this
|
||||||
module. See module :mod:`glob` for pathname expansion (:mod:`glob` uses
|
module. See module :mod:`glob` for pathname expansion (:mod:`glob` uses
|
||||||
|
|
|
@ -1340,7 +1340,7 @@ are always available. They are listed here in alphabetical order.
|
||||||
single: I/O control; buffering
|
single: I/O control; buffering
|
||||||
single: binary mode
|
single: binary mode
|
||||||
single: text mode
|
single: text mode
|
||||||
module: sys
|
pair: module; sys
|
||||||
|
|
||||||
See also the file handling modules, such as :mod:`fileinput`, :mod:`io`
|
See also the file handling modules, such as :mod:`fileinput`, :mod:`io`
|
||||||
(where :func:`open` is declared), :mod:`os`, :mod:`os.path`, :mod:`tempfile`,
|
(where :func:`open` is declared), :mod:`os`, :mod:`os.path`, :mod:`tempfile`,
|
||||||
|
@ -1987,7 +1987,7 @@ are always available. They are listed here in alphabetical order.
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
statement: import
|
statement: import
|
||||||
module: builtins
|
pair: module; builtins
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
|
|
|
@ -10,7 +10,7 @@
|
||||||
pair: HTTP; protocol
|
pair: HTTP; protocol
|
||||||
single: HTTP; http.client (standard module)
|
single: HTTP; http.client (standard module)
|
||||||
|
|
||||||
.. index:: module: urllib.request
|
.. index:: pair: module; urllib.request
|
||||||
|
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
|
|
|
@ -9,7 +9,7 @@ Internet Protocols and Support
|
||||||
single: Internet
|
single: Internet
|
||||||
single: World Wide Web
|
single: World Wide Web
|
||||||
|
|
||||||
.. index:: module: socket
|
.. index:: pair: module; socket
|
||||||
|
|
||||||
The modules described in this chapter implement internet protocols and support
|
The modules described in this chapter implement internet protocols and support
|
||||||
for related technology. They are all implemented in Python. Most of these
|
for related technology. They are all implemented in Python. Most of these
|
||||||
|
|
|
@ -16,7 +16,7 @@ functionality. The POSIX locale mechanism allows programmers to deal with
|
||||||
certain cultural issues in an application, without requiring the programmer to
|
certain cultural issues in an application, without requiring the programmer to
|
||||||
know all the specifics of each country where the software is executed.
|
know all the specifics of each country where the software is executed.
|
||||||
|
|
||||||
.. index:: module: _locale
|
.. index:: pair: module; _locale
|
||||||
|
|
||||||
The :mod:`locale` module is implemented on top of the :mod:`_locale` module,
|
The :mod:`locale` module is implemented on top of the :mod:`_locale` module,
|
||||||
which in turn uses an ANSI C locale implementation if available.
|
which in turn uses an ANSI C locale implementation if available.
|
||||||
|
@ -464,7 +464,7 @@ The :mod:`locale` module defines the following exception and functions:
|
||||||
|
|
||||||
.. data:: LC_CTYPE
|
.. data:: LC_CTYPE
|
||||||
|
|
||||||
.. index:: module: string
|
.. index:: pair: module; string
|
||||||
|
|
||||||
Locale category for the character type functions. Depending on the settings of
|
Locale category for the character type functions. Depending on the settings of
|
||||||
this category, the functions of module :mod:`string` dealing with case change
|
this category, the functions of module :mod:`string` dealing with case change
|
||||||
|
|
|
@ -15,8 +15,8 @@ undocumented on purpose; it may change between Python versions (although it
|
||||||
rarely does). [#]_
|
rarely does). [#]_
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
module: pickle
|
pair: module; pickle
|
||||||
module: shelve
|
pair: module; shelve
|
||||||
|
|
||||||
This is not a general "persistence" module. For general persistence and
|
This is not a general "persistence" module. For general persistence and
|
||||||
transfer of Python objects through RPC calls, see the modules :mod:`pickle` and
|
transfer of Python objects through RPC calls, see the modules :mod:`pickle` and
|
||||||
|
|
|
@ -159,7 +159,7 @@ the :mod:`glob` module.)
|
||||||
On Unix and Windows, return the argument with an initial component of ``~`` or
|
On Unix and Windows, return the argument with an initial component of ``~`` or
|
||||||
``~user`` replaced by that *user*'s home directory.
|
``~user`` replaced by that *user*'s home directory.
|
||||||
|
|
||||||
.. index:: module: pwd
|
.. index:: pair: module; pwd
|
||||||
|
|
||||||
On Unix, an initial ``~`` is replaced by the environment variable :envvar:`HOME`
|
On Unix, an initial ``~`` is replaced by the environment variable :envvar:`HOME`
|
||||||
if it is set; otherwise the current user's home directory is looked up in the
|
if it is set; otherwise the current user's home directory is looked up in the
|
||||||
|
|
|
@ -1284,7 +1284,7 @@ or `the MSDN <https://msdn.microsoft.com/en-us/library/z0kc8e3z.aspx>`_ on Windo
|
||||||
|
|
||||||
.. function:: openpty()
|
.. function:: openpty()
|
||||||
|
|
||||||
.. index:: module: pty
|
.. index:: pair: module; pty
|
||||||
|
|
||||||
Open a new pseudo-terminal pair. Return a pair of file descriptors
|
Open a new pseudo-terminal pair. Return a pair of file descriptors
|
||||||
``(master, slave)`` for the pty and the tty, respectively. The new file
|
``(master, slave)`` for the pty and the tty, respectively. The new file
|
||||||
|
@ -2890,7 +2890,7 @@ features:
|
||||||
possible and call :func:`lstat` on the result. This does not apply to
|
possible and call :func:`lstat` on the result. This does not apply to
|
||||||
dangling symlinks or junction points, which will raise the usual exceptions.
|
dangling symlinks or junction points, which will raise the usual exceptions.
|
||||||
|
|
||||||
.. index:: module: stat
|
.. index:: pair: module; stat
|
||||||
|
|
||||||
Example::
|
Example::
|
||||||
|
|
||||||
|
|
|
@ -20,8 +20,8 @@ supports post-mortem debugging and can be called under program control.
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
single: Pdb (class in pdb)
|
single: Pdb (class in pdb)
|
||||||
module: bdb
|
pair: module; bdb
|
||||||
module: cmd
|
pair: module; cmd
|
||||||
|
|
||||||
The debugger is extensible -- it is actually defined as the class :class:`Pdb`.
|
The debugger is extensible -- it is actually defined as the class :class:`Pdb`.
|
||||||
This is currently undocumented but easily understood by reading the source. The
|
This is currently undocumented but easily understood by reading the source. The
|
||||||
|
|
|
@ -11,7 +11,7 @@ This module provides access to operating system functionality that is
|
||||||
standardized by the C Standard and the POSIX standard (a thinly disguised Unix
|
standardized by the C Standard and the POSIX standard (a thinly disguised Unix
|
||||||
interface).
|
interface).
|
||||||
|
|
||||||
.. index:: module: os
|
.. index:: pair: module; os
|
||||||
|
|
||||||
**Do not import this module directly.** Instead, import the module :mod:`os`,
|
**Do not import this module directly.** Instead, import the module :mod:`os`,
|
||||||
which provides a *portable* version of this interface. On Unix, the :mod:`os`
|
which provides a *portable* version of this interface. On Unix, the :mod:`os`
|
||||||
|
|
|
@ -39,7 +39,7 @@ raised if the entry asked for cannot be found.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
.. index:: module: crypt
|
.. index:: pair: module; crypt
|
||||||
|
|
||||||
In traditional Unix the field ``pw_passwd`` usually contains a password
|
In traditional Unix the field ``pw_passwd`` usually contains a password
|
||||||
encrypted with a DES derived algorithm (see module :mod:`crypt`). However most
|
encrypted with a DES derived algorithm (see module :mod:`crypt`). However most
|
||||||
|
|
|
@ -33,7 +33,7 @@ can be set to handler functions. When an XML document is then fed to the
|
||||||
parser, the handler functions are called for the character data and markup in
|
parser, the handler functions are called for the character data and markup in
|
||||||
the XML document.
|
the XML document.
|
||||||
|
|
||||||
.. index:: module: pyexpat
|
.. index:: pair: module; pyexpat
|
||||||
|
|
||||||
This module uses the :mod:`pyexpat` module to provide access to the Expat
|
This module uses the :mod:`pyexpat` module to provide access to the Expat
|
||||||
parser. Direct use of the :mod:`pyexpat` module is deprecated.
|
parser. Direct use of the :mod:`pyexpat` module is deprecated.
|
||||||
|
|
|
@ -30,7 +30,7 @@ The :mod:`runpy` module provides two functions:
|
||||||
.. function:: run_module(mod_name, init_globals=None, run_name=None, alter_sys=False)
|
.. function:: run_module(mod_name, init_globals=None, run_name=None, alter_sys=False)
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
module: __main__
|
pair: module; __main__
|
||||||
|
|
||||||
Execute the code of the specified module and return the resulting module
|
Execute the code of the specified module and return the resulting module
|
||||||
globals dictionary. The module's code is first located using the standard
|
globals dictionary. The module's code is first located using the standard
|
||||||
|
@ -101,7 +101,7 @@ The :mod:`runpy` module provides two functions:
|
||||||
.. function:: run_path(path_name, init_globals=None, run_name=None)
|
.. function:: run_path(path_name, init_globals=None, run_name=None)
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
module: __main__
|
pair: module; __main__
|
||||||
|
|
||||||
Execute the code at the named filesystem location and return the resulting
|
Execute the code at the named filesystem location and return the resulting
|
||||||
module globals dictionary. As with a script name supplied to the CPython
|
module globals dictionary. As with a script name supplied to the CPython
|
||||||
|
|
|
@ -6,7 +6,7 @@
|
||||||
|
|
||||||
**Source code:** :source:`Lib/shelve.py`
|
**Source code:** :source:`Lib/shelve.py`
|
||||||
|
|
||||||
.. index:: module: pickle
|
.. index:: pair: module; pickle
|
||||||
|
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
|
@ -95,8 +95,8 @@ Restrictions
|
||||||
------------
|
------------
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
module: dbm.ndbm
|
pair: module; dbm.ndbm
|
||||||
module: dbm.gnu
|
pair: module; dbm.gnu
|
||||||
|
|
||||||
* The choice of which database package will be used (such as :mod:`dbm.ndbm` or
|
* The choice of which database package will be used (such as :mod:`dbm.ndbm` or
|
||||||
:mod:`dbm.gnu`) depends on which interface is available. Therefore it is not
|
:mod:`dbm.gnu`) depends on which interface is available. Therefore it is not
|
||||||
|
|
|
@ -109,7 +109,7 @@ directory precedes the :file:`foo` directory because :file:`bar.pth` comes
|
||||||
alphabetically before :file:`foo.pth`; and :file:`spam` is omitted because it is
|
alphabetically before :file:`foo.pth`; and :file:`spam` is omitted because it is
|
||||||
not mentioned in either path configuration file.
|
not mentioned in either path configuration file.
|
||||||
|
|
||||||
.. index:: module: sitecustomize
|
.. index:: pair: module; sitecustomize
|
||||||
|
|
||||||
After these path manipulations, an attempt is made to import a module named
|
After these path manipulations, an attempt is made to import a module named
|
||||||
:mod:`sitecustomize`, which can perform arbitrary site-specific customizations.
|
:mod:`sitecustomize`, which can perform arbitrary site-specific customizations.
|
||||||
|
@ -121,7 +121,7 @@ with :file:`pythonw.exe` on Windows (which is used by default to start IDLE),
|
||||||
attempted output from :mod:`sitecustomize` is ignored. Any other exception
|
attempted output from :mod:`sitecustomize` is ignored. Any other exception
|
||||||
causes a silent and perhaps mysterious failure of the process.
|
causes a silent and perhaps mysterious failure of the process.
|
||||||
|
|
||||||
.. index:: module: usercustomize
|
.. index:: pair: module; usercustomize
|
||||||
|
|
||||||
After this, an attempt is made to import a module named :mod:`usercustomize`,
|
After this, an attempt is made to import a module named :mod:`usercustomize`,
|
||||||
which can perform arbitrary user-specific customizations, if
|
which can perform arbitrary user-specific customizations, if
|
||||||
|
|
|
@ -1916,7 +1916,7 @@ to sockets.
|
||||||
.. method:: socket.setsockopt(level, optname, None, optlen: int)
|
.. method:: socket.setsockopt(level, optname, None, optlen: int)
|
||||||
:noindex:
|
:noindex:
|
||||||
|
|
||||||
.. index:: module: struct
|
.. index:: pair: module; struct
|
||||||
|
|
||||||
Set the value of the given socket option (see the Unix manual page
|
Set the value of the given socket option (see the Unix manual page
|
||||||
:manpage:`setsockopt(2)`). The needed symbolic constants are defined in the
|
:manpage:`setsockopt(2)`). The needed symbolic constants are defined in the
|
||||||
|
|
|
@ -330,7 +330,7 @@ Notes:
|
||||||
|
|
||||||
(3)
|
(3)
|
||||||
.. index::
|
.. index::
|
||||||
module: math
|
pair: module; math
|
||||||
single: floor() (in module math)
|
single: floor() (in module math)
|
||||||
single: ceil() (in module math)
|
single: ceil() (in module math)
|
||||||
single: trunc() (in module math)
|
single: trunc() (in module math)
|
||||||
|
@ -1600,7 +1600,7 @@ String Methods
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
module: re
|
pair: module; re
|
||||||
|
|
||||||
Strings implement all of the :ref:`common <typesseq-common>` sequence
|
Strings implement all of the :ref:`common <typesseq-common>` sequence
|
||||||
operations, along with the additional methods described below.
|
operations, along with the additional methods described below.
|
||||||
|
@ -2511,7 +2511,7 @@ Binary Sequence Types --- :class:`bytes`, :class:`bytearray`, :class:`memoryview
|
||||||
object: bytes
|
object: bytes
|
||||||
object: bytearray
|
object: bytearray
|
||||||
object: memoryview
|
object: memoryview
|
||||||
module: array
|
pair: module; array
|
||||||
|
|
||||||
The core built-in types for manipulating binary data are :class:`bytes` and
|
The core built-in types for manipulating binary data are :class:`bytes` and
|
||||||
:class:`bytearray`. They are supported by :class:`memoryview` which uses
|
:class:`bytearray`. They are supported by :class:`memoryview` which uses
|
||||||
|
@ -5378,7 +5378,7 @@ Type Objects
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
builtin: type
|
builtin: type
|
||||||
module: types
|
pair: module; types
|
||||||
|
|
||||||
Type objects represent the various object types. An object's type is accessed
|
Type objects represent the various object types. An object's type is accessed
|
||||||
by the built-in function :func:`type`. There are no special operations on
|
by the built-in function :func:`type`. There are no special operations on
|
||||||
|
|
|
@ -297,7 +297,7 @@ traceback attached to them, they form a reference cycle with the stack frame,
|
||||||
keeping all locals in that frame alive until the next garbage collection occurs.
|
keeping all locals in that frame alive until the next garbage collection occurs.
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
module: sys
|
pair: module; sys
|
||||||
object: traceback
|
object: traceback
|
||||||
|
|
||||||
Before an :keyword:`!except` clause's suite is executed,
|
Before an :keyword:`!except` clause's suite is executed,
|
||||||
|
|
|
@ -377,7 +377,7 @@ Sequences
|
||||||
(and hence unhashable), byte arrays otherwise provide the same interface
|
(and hence unhashable), byte arrays otherwise provide the same interface
|
||||||
and functionality as immutable :class:`bytes` objects.
|
and functionality as immutable :class:`bytes` objects.
|
||||||
|
|
||||||
.. index:: module: array
|
.. index:: pair: module; array
|
||||||
|
|
||||||
The extension module :mod:`array` provides an additional example of a
|
The extension module :mod:`array` provides an additional example of a
|
||||||
mutable sequence type, as does the :mod:`collections` module.
|
mutable sequence type, as does the :mod:`collections` module.
|
||||||
|
@ -451,8 +451,8 @@ Mappings
|
||||||
section :ref:`dict`).
|
section :ref:`dict`).
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
module: dbm.ndbm
|
pair: module; dbm.ndbm
|
||||||
module: dbm.gnu
|
pair: module; dbm.gnu
|
||||||
|
|
||||||
The extension modules :mod:`dbm.ndbm` and :mod:`dbm.gnu` provide
|
The extension modules :mod:`dbm.ndbm` and :mod:`dbm.gnu` provide
|
||||||
additional examples of mapping types, as does the :mod:`collections`
|
additional examples of mapping types, as does the :mod:`collections`
|
||||||
|
@ -909,7 +909,7 @@ Class instances
|
||||||
I/O objects (also known as file objects)
|
I/O objects (also known as file objects)
|
||||||
.. index::
|
.. index::
|
||||||
builtin: open
|
builtin: open
|
||||||
module: io
|
pair: module; io
|
||||||
single: popen() (in module os)
|
single: popen() (in module os)
|
||||||
single: makefile() (socket method)
|
single: makefile() (socket method)
|
||||||
single: sys.stdin
|
single: sys.stdin
|
||||||
|
|
|
@ -151,7 +151,7 @@ to previously bound variables in the nearest enclosing function scope.
|
||||||
:exc:`SyntaxError` is raised at compile time if the given name does not
|
:exc:`SyntaxError` is raised at compile time if the given name does not
|
||||||
exist in any enclosing function scope.
|
exist in any enclosing function scope.
|
||||||
|
|
||||||
.. index:: module: __main__
|
.. index:: pair: module; __main__
|
||||||
|
|
||||||
The namespace for a module is automatically created the first time a module is
|
The namespace for a module is automatically created the first time a module is
|
||||||
imported. The main module for a script is always called :mod:`__main__`.
|
imported. The main module for a script is always called :mod:`__main__`.
|
||||||
|
|
|
@ -21,9 +21,9 @@ Complete Python programs
|
||||||
.. index:: single: program
|
.. index:: single: program
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
module: sys
|
pair: module; sys
|
||||||
module: __main__
|
pair: module; __main__
|
||||||
module: builtins
|
pair: module; builtins
|
||||||
|
|
||||||
While a language specification need not prescribe how the language interpreter
|
While a language specification need not prescribe how the language interpreter
|
||||||
is invoked, it is useful to have a notion of a complete Python program. A
|
is invoked, it is useful to have a notion of a complete Python program. A
|
||||||
|
@ -38,7 +38,7 @@ the next section.
|
||||||
|
|
||||||
.. index::
|
.. index::
|
||||||
single: interactive mode
|
single: interactive mode
|
||||||
module: __main__
|
pair: module; __main__
|
||||||
|
|
||||||
The interpreter may also be invoked in interactive mode; in this case, it does
|
The interpreter may also be invoked in interactive mode; in this case, it does
|
||||||
not read and execute a complete program but reads and executes one statement
|
not read and execute a complete program but reads and executes one statement
|
||||||
|
|
|
@ -689,7 +689,7 @@ def patch_pairindextypes(app) -> None:
|
||||||
# away from this, we need Sphinx to believe that these values don't
|
# away from this, we need Sphinx to believe that these values don't
|
||||||
# exist, by deleting them when using the gettext builder.
|
# exist, by deleting them when using the gettext builder.
|
||||||
|
|
||||||
# pairindextypes.pop('module', None)
|
pairindextypes.pop('module', None)
|
||||||
# pairindextypes.pop('keyword', None)
|
# pairindextypes.pop('keyword', None)
|
||||||
# pairindextypes.pop('operator', None)
|
# pairindextypes.pop('operator', None)
|
||||||
# pairindextypes.pop('object', None)
|
# pairindextypes.pop('object', None)
|
||||||
|
@ -697,10 +697,6 @@ def patch_pairindextypes(app) -> None:
|
||||||
# pairindextypes.pop('statement', None)
|
# pairindextypes.pop('statement', None)
|
||||||
# pairindextypes.pop('builtin', None)
|
# pairindextypes.pop('builtin', None)
|
||||||
|
|
||||||
# there needs to be at least one statement in this block, will be
|
|
||||||
# removed when the first of the below is uncommented.
|
|
||||||
pass
|
|
||||||
|
|
||||||
|
|
||||||
def setup(app):
|
def setup(app):
|
||||||
app.add_role('issue', issue_role)
|
app.add_role('issue', issue_role)
|
||||||
|
|
|
@ -466,7 +466,7 @@ Reference for a complete guide to file objects.
|
||||||
Saving structured data with :mod:`json`
|
Saving structured data with :mod:`json`
|
||||||
---------------------------------------
|
---------------------------------------
|
||||||
|
|
||||||
.. index:: module: json
|
.. index:: pair: module; json
|
||||||
|
|
||||||
Strings can easily be written to and read from a file. Numbers take a bit more
|
Strings can easily be written to and read from a file. Numbers take a bit more
|
||||||
effort, since the :meth:`read` method only returns strings, which will have to
|
effort, since the :meth:`read` method only returns strings, which will have to
|
||||||
|
|
|
@ -264,7 +264,7 @@ Some tips for experts:
|
||||||
Standard Modules
|
Standard Modules
|
||||||
================
|
================
|
||||||
|
|
||||||
.. index:: module: sys
|
.. index:: pair: module; sys
|
||||||
|
|
||||||
Python comes with a library of standard modules, described in a separate
|
Python comes with a library of standard modules, described in a separate
|
||||||
document, the Python Library Reference ("Library Reference" hereafter). Some
|
document, the Python Library Reference ("Library Reference" hereafter). Some
|
||||||
|
@ -345,7 +345,7 @@ Without arguments, :func:`dir` lists the names you have defined currently::
|
||||||
|
|
||||||
Note that it lists all types of names: variables, modules, functions, etc.
|
Note that it lists all types of names: variables, modules, functions, etc.
|
||||||
|
|
||||||
.. index:: module: builtins
|
.. index:: pair: module; builtins
|
||||||
|
|
||||||
:func:`dir` does not list the names of built-in functions and variables. If you
|
:func:`dir` does not list the names of built-in functions and variables. If you
|
||||||
want a list of those, they are defined in the standard module
|
want a list of those, they are defined in the standard module
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue