Return the line number of the instruction that occurs on or before ``byte_offset`` and ends after it.
If you just need the line number of a frame, use :c:func:`PyFrame_GetLineNumber` instead.
- For efficiently iterating over the line numbers in a code object, use `the API described in PEP 626
- <https://peps.python.org/pep-0626/#out-of-process-debuggers-and-profilers>`_.
+ For efficiently iterating over the line numbers in a code object, use :pep:`the API described in PEP 626
+ <0626#out-of-process-debuggers-and-profilers>`.
.. c:function:: int PyCode_Addr2Location(PyObject *co, int byte_offset, int *start_line, int *start_column, int *end_line, int *end_column)
``NULL``, use :c:func:`Py_XINCREF`.
Do not expect this function to actually modify *o* in any way.
- For at least `some objects <https://peps.python.org/pep-0683/>`_,
+ For at least :pep:`some objects <0683>`,
this function has no effect.
.. versionchanged:: 3.12
use :c:func:`Py_XDECREF`.
Do not expect this function to actually modify *o* in any way.
- For at least `some objects <https://peps.python.org/pep-0683/>`_,
+ For at least :pep:`some objects <683>`,
this function has no effect.
.. warning::
The latest stable releases can always be found on the `Python download page
<https://www.python.org/downloads/>`_. There are two production-ready versions
of Python: 2.x and 3.x. The recommended version is 3.x, which is supported by
-most widely used libraries. Although 2.x is still widely used, `it is not
-maintained anymore <https://peps.python.org/pep-0373/>`_.
+most widely used libraries. Although 2.x is still widely used, :pep:`it is not
+maintained anymore <0373>`.
How many people are using Python?
---------------------------------
* ``name`` is a raw string for the class name
* ``bases`` is a list of nodes for explicitly specified base classes.
* ``keywords`` is a list of :class:`.keyword` nodes, principally for 'metaclass'.
- Other keywords will be passed to the metaclass, as per `PEP-3115
- <https://peps.python.org/pep-3115/>`_.
+ Other keywords will be passed to the metaclass, as per :pep:`3115`.
* ``body`` is a list of nodes representing the code within the class
definition.
* ``decorator_list`` is a list of nodes, as in :class:`FunctionDef`.
The mappings from SQLite threading modes to DB-API 2.0 threadsafety levels
are as follows:
- +------------------+-----------------+----------------------+-------------------------------+
- | SQLite threading | `threadsafety`_ | `SQLITE_THREADSAFE`_ | DB-API 2.0 meaning |
- | mode | | | |
- +==================+=================+======================+===============================+
- | single-thread | 0 | 0 | Threads may not share the |
- | | | | module |
- +------------------+-----------------+----------------------+-------------------------------+
- | multi-thread | 1 | 2 | Threads may share the module, |
- | | | | but not connections |
- +------------------+-----------------+----------------------+-------------------------------+
- | serialized | 3 | 1 | Threads may share the module, |
- | | | | connections and cursors |
- +------------------+-----------------+----------------------+-------------------------------+
-
- .. _threadsafety: https://peps.python.org/pep-0249/#threadsafety
+ +------------------+----------------------+----------------------+-------------------------------+
+ | SQLite threading | :pep:`threadsafety | `SQLITE_THREADSAFE`_ | DB-API 2.0 meaning |
+ | mode | <0249#threadsafety>` | | |
+ +==================+======================+======================+===============================+
+ | single-thread | 0 | 0 | Threads may not share the |
+ | | | | module |
+ +------------------+----------------------+----------------------+-------------------------------+
+ | multi-thread | 1 | 2 | Threads may share the module, |
+ | | | | but not connections |
+ +------------------+----------------------+----------------------+-------------------------------+
+ | serialized | 3 | 1 | Threads may share the module, |
+ | | | | connections and cursors |
+ +------------------+----------------------+----------------------+-------------------------------+
+
.. _SQLITE_THREADSAFE: https://sqlite.org/compile.html#threadsafe
.. versionchanged:: 3.11
.. class:: StartResponse()
- A :class:`typing.Protocol` describing `start_response()
- <https://peps.python.org/pep-3333/#the-start-response-callable>`_
+ A :class:`typing.Protocol` describing :pep:`start_response()
+ <3333#the-start-response-callable>`
callables (:pep:`3333`).
.. data:: WSGIEnvironment
.. class:: InputStream()
- A :class:`typing.Protocol` describing a `WSGI Input Stream
- <https://peps.python.org/pep-3333/#input-and-error-streams>`_.
+ A :class:`typing.Protocol` describing a :pep:`WSGI Input Stream
+ <3333#input-and-error-streams>`.
.. class:: ErrorStream()
- A :class:`typing.Protocol` describing a `WSGI Error Stream
- <https://peps.python.org/pep-3333/#input-and-error-streams>`_.
+ A :class:`typing.Protocol` describing a :pep:`WSGI Error Stream
+ <3333#input-and-error-streams>`.
.. class:: FileWrapper()
- A :class:`typing.Protocol` describing a `file wrapper
- <https://peps.python.org/pep-3333/#optional-platform-specific-file-handling>`_.
+ A :class:`typing.Protocol` describing a :pep:`file wrapper
+ <3333#optional-platform-specific-file-handling>`.
See :class:`wsgiref.util.FileWrapper` for a concrete implementation of this
protocol.
line by default, otherwise it can still be accessed through the Python
launcher for Windows as ``py -m pip``.
-As `discussed in the PEP`__, platform packagers may choose not to install
+As :pep:`discussed in the PEP <0477#disabling-ensurepip-by-downstream-distributors>`,
+platform packagers may choose not to install
these commands by default, as long as, when invoked, they provide clear and
simple directions on how to install them on that platform (usually using
the system package manager).
-__ https://peps.python.org/pep-0477/#disabling-ensurepip-by-downstream-distributors
-
-
Documentation Changes
~~~~~~~~~~~~~~~~~~~~~
reducing the size of every :class:`str` object by at least 8 bytes.
* :pep:`632`: Remove the :mod:`!distutils` package.
- See `the migration guide <https://peps.python.org/pep-0632/#migration-advice>`_
+ See :pep:`the migration guide <0632#migration-advice>`
for advice replacing the APIs it provided.
The third-party `Setuptools <https://setuptools.pypa.io/en/latest/deprecated/distutils-legacy.html>`__
package continues to provide :mod:`!distutils`,
line by default, otherwise it can still be accessed through the Python
launcher for Windows as ``py -m pip``.
-As `discussed in the PEP`__, platform packagers may choose not to install
+As :pep:`discussed in the PEP <0453#recommendations-for-downstream-distributors>`
+platform packagers may choose not to install
these commands by default, as long as, when invoked, they provide clear and
simple directions on how to install them on that platform (usually using
the system package manager).
-__ https://peps.python.org/pep-0453/#recommendations-for-downstream-distributors
-
.. note::
To avoid conflicts between parallel Python 2 and Python 3 installations,
The new functions return the number of nanoseconds as an integer value.
-`Measurements <https://peps.python.org/pep-0564/#annex-clocks-resolution-in-python>`_
+:pep:`Measurements <0564#annex-clocks-resolution-in-python>`
show that on Linux and Windows the resolution of :func:`time.time_ns` is
approximately 3 times better than that of :func:`time.time`.
.. section: Documentation
All docstrings in code snippets are now wrapped into :c:macro:`PyDoc_STR` to
-follow the guideline of `PEP 7's Documentation Strings paragraph
-<https://www.python.org/dev/peps/pep-0007/#documentation-strings>`_. Patch
+follow the guideline of :pep:`PEP 7's Documentation Strings paragraph
+<0007#documentation-strings>`. Patch
by Oleg Iarygin.
..
projects / thirdparty / Python / cpython.git / commitdiff
