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
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.
.. _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>`).
.. _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'