mirror of
https://github.com/python/cpython.git
synced 2025-10-19 16:03:42 +00:00
Remove duplicate words in the documentation (#140221)
This commit is contained in:
parent
459d493ce3
commit
2ebd0cdb16
5 changed files with 6 additions and 6 deletions
|
@ -294,7 +294,7 @@ The full API is described below for advanced use cases.
|
|||
Default flags, based on current values of macros such as
|
||||
:c:macro:`Py_LIMITED_API` and :c:macro:`Py_GIL_DISABLED`.
|
||||
|
||||
Alternately, the field can be set to to the following flags, combined
|
||||
Alternately, the field can be set to the following flags, combined
|
||||
by bitwise OR.
|
||||
Unused bits must be set to zero.
|
||||
|
||||
|
|
|
@ -1257,7 +1257,7 @@ find and load modules.
|
|||
To accommodate this requirement, when running on iOS, extension module
|
||||
binaries are *not* packaged as ``.so`` files on ``sys.path``, but as
|
||||
individual standalone frameworks. To discover those frameworks, this loader
|
||||
is be registered against the ``.fwork`` file extension, with a ``.fwork``
|
||||
is registered against the ``.fwork`` file extension, with a ``.fwork``
|
||||
file acting as a placeholder in the original location of the binary on
|
||||
``sys.path``. The ``.fwork`` file contains the path of the actual binary in
|
||||
the ``Frameworks`` folder, relative to the app bundle. To allow for
|
||||
|
|
|
@ -5944,7 +5944,7 @@ It is written as ``None``.
|
|||
The Ellipsis Object
|
||||
-------------------
|
||||
|
||||
This object is commonly used used to indicate that something is omitted.
|
||||
This object is commonly used to indicate that something is omitted.
|
||||
It supports no special operations. There is exactly one ellipsis object, named
|
||||
:const:`Ellipsis` (a built-in name). ``type(Ellipsis)()`` produces the
|
||||
:const:`Ellipsis` singleton.
|
||||
|
|
|
@ -1140,7 +1140,7 @@ concurrent.futures
|
|||
.. _whatsnew314-concurrent-futures-start-method:
|
||||
|
||||
* On Unix platforms other than macOS, :ref:`'forkserver'
|
||||
<multiprocessing-start-method-forkserver>` is now the the default :ref:`start
|
||||
<multiprocessing-start-method-forkserver>` is now the default :ref:`start
|
||||
method <multiprocessing-start-methods>` for
|
||||
:class:`~concurrent.futures.ProcessPoolExecutor`
|
||||
(replacing :ref:`'fork' <multiprocessing-start-method-fork>`).
|
||||
|
@ -1591,7 +1591,7 @@ multiprocessing
|
|||
.. _whatsnew314-multiprocessing-start-method:
|
||||
|
||||
* On Unix platforms other than macOS, :ref:`'forkserver'
|
||||
<multiprocessing-start-method-forkserver>` is now the the default :ref:`start
|
||||
<multiprocessing-start-method-forkserver>` is now the default :ref:`start
|
||||
method <multiprocessing-start-methods>`
|
||||
(replacing :ref:`'fork' <multiprocessing-start-method-fork>`).
|
||||
This change does not affect Windows or macOS, where :ref:`'spawn'
|
||||
|
|
|
@ -1010,7 +1010,7 @@ Deprecated C APIs
|
|||
use the :c:type:`PyBytesWriter` API instead.
|
||||
(Contributed by Victor Stinner in :gh:`129813`.)
|
||||
|
||||
* Deprecate :c:member:`~PyComplexObject.cval` field of the the
|
||||
* Deprecate :c:member:`~PyComplexObject.cval` field of the
|
||||
:c:type:`PyComplexObject` type.
|
||||
Use :c:func:`PyComplex_AsCComplex` and :c:func:`PyComplex_FromCComplex`
|
||||
to convert a Python complex number to/from the C :c:type:`Py_complex`
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue