🔍 Translation review needed after CPython sync (2026-10-13) #99

Python's :term:`generators <generator>` -- or more precisely, :term:`generator functions <generator function>` and :term:`generator iterators <generator iterat…
A function that contains one or more :ref:`yield expressions <yieldexpr>` is a :term:`generator function`. For example::
>>> def count_to_three():\n...     yield 0\n...     yield 1\n...     yield 2\n...     yield 3
Generator functions behave as regular :ref:`user-defined functions <user-defined-funcs>` (for example, they have the same attributes), except that calling a ge…
>>> count_to_three()\n<generator object count_to_three at 0x7f33a2305000>
Iterating a generator iterator executes code of the underlying generator function, producing each :keyword:`yield`\ed value in turn::
>>> for number in count_to_three():\n...     print(number)\n0\n1\n2\n3\n\n>>> list(count_to_three())\n[0, 1, 2, 3]
One common use for generator functions is implementing the :meth:`~object.__iter__` method of custom iterable objects. For example::
>>> class CardDeck:\n...     def __iter__(self):\n...         yield 'three of clubs'\n...         yield 'ace of hearts'\n\n>>> list(CardDeck())\n['three of clu…
Generator iterators implement the :ref:`iterator protocol <stdtypes-iterators>`. Iterating them drives execution of the underlying generator function.
Starts the execution of a generator function or resumes it at the :ref:`yield expression <yieldexpr>` where the function is currently suspended. When a generat…
This method is normally called implicitly, for example by a :keyword:`for` loop, or by the built-in :func:`next` function.
Generator iterators have a few more methods than generic iterators, which can be used to control the execution of the underlying generator function:
"Sends" a value into the generator function: the *value* argument becomes the result of the current yield expression.
Otherwise, this method behaves like :meth:`~generator.__next__`: it resumes the underlying function and either returns the next yielded value or raises :exc:`S…
When :meth:`send` is called to start the generator, it must be called with :const:`None` as the argument, because there is no current yield expression that cou…
Raises an exception at the point where the generator is currently suspended.
Otherwise, this method behaves like :meth:`~generator.__next__`: it resumes the underlying function and either returns the next yielded value or raises :exc:`S…
When :meth:`throw` is called to start the generator, the generator immediately exits (that is, subsequent calls to :meth:`~generator.__next__` will raise :exc:…
In typical use, this is called with a single argument, an exception instance, similar to the way the :keyword:`raise` keyword is used.
For backwards compatibility, however, the second signature is supported, following a convention from older versions of Python. The *type* argument should be an…
The second signature \(type\[, value\[, traceback\]\]\) is deprecated and may be removed in a future version of Python.
Raises a :exc:`GeneratorExit` exception at the point where the generator function is currently suspended (equivalent to calling ``throw(GeneratorExit)``).
If the generator function has already exited (due to an exception or normal return), or raises :exc:`GeneratorExit` (by not catching the exception), :meth:`clo…
When a generator iterator is garbage collected before it has exited, :meth:`~generator.close` is called automatically.
… and 19 more

*spawn* is now the default start method when there is no writable temporary directory, for example on a read-only file system. Previously *forkserver* remained…

:gh:`158918`: Reduce C stack usage of ``_PyModule_IsPossiblyShadowing``, which could potentially cause stack overflows during module attribute access while dee…
:gh:`158824`: Fix module-level :meth:`~module.__getattr__` being called before a module's own lazy imports were resolved, which allowed it to shadow them.
:gh:`158219`: Fix :class:`bytearray` constructor: do not use a bytes object if its hash value is already computed. Patch by Cody Maloney and Victor Stinner.
:gh:`157468`: Fix the JIT optimizer folding a builtin name to a constant taken from the interpreter's builtins dictionary even when the running function uses a…
:gh:`157242`: :class:`io.BytesIO` is no longer closed on ``write()`` and ``truncate()`` failure (:exc:`MemoryError`). Patch by Victor Stinner.
:gh:`156920`: Fix :mod:`asyncio` on Windows: closing a :class:`~asyncio.DatagramTransport` under :class:`~asyncio.ProactorEventLoop` while datagrams were still…
:gh:`156698`: Fix :class:`asyncio.ProactorEventLoop` UDP transports so that a write error no longer strands a paused protocol: the write loop is now reschedule…
:gh:`155717`: :mod:`multiprocessing`'s default start method is now :ref:`"spawn" <multiprocessing-start-methods>` instead of ``"forkserver"`` when there is no …
:gh:`154594`: Fix :func:`copy.deepcopy` so that an object whose deep copy is ``None`` is still memoized. Patch by tonghuaroot.
:gh:`142083`: Document the ``'w'`` type code in the :class:`array.array` docstring, so that it lists the same type codes as :data:`array.typecodes` and the :mo…