pep 525: Fix formatting

This commit is contained in:
Yury Selivanov 2016-09-06 17:09:13 -07:00
parent be5a9b53d3
commit 8f8cdb00ed
1 changed files with 14 additions and 12 deletions

View File

@ -260,20 +260,22 @@ with ``firstiter`` and ``finalizer`` fields.
asyncio
-------
The asyncio event loop will use ``sys.set_asyncgen_hooks()`` API to maintain
a weak set of all scheduled asynchronous generators, and to schedule their
``aclose()`` coroutine methods when it is time for generators to be GCed.
The asyncio event loop will use ``sys.set_asyncgen_hooks()`` API to
maintain a weak set of all scheduled asynchronous generators, and to
schedule their ``aclose()`` coroutine methods when it is time for
generators to be GCed.
To make sure that asyncio programs can finalize all scheduled asynchronous
generators reliably, we propose to add a new event loop method
``loop.shutdown_asyncgens(*, timeout=30)``. The method will schedule all
currently open asynchronous generators to close with an ``aclose()`` call.
To make sure that asyncio programs can finalize all scheduled
asynchronous generators reliably, we propose to add a new event loop
method ``loop.shutdown_asyncgens(*, timeout=30)``. The method will
schedule all currently open asynchronous generators to close with an
``aclose()`` call.
After calling the ``loop.shutdown_asyncgens()`` method, the event loop will
issue a warning whenever a new asynchronous generator is iterated for the first
time. The idea is that after requesting all asynchronous generators to be
shutdown, the program should not execute code that iterates over new
asynchronous generators.
After calling the ``loop.shutdown_asyncgens()`` method, the event loop
will issue a warning whenever a new asynchronous generator is iterated
for the first time. The idea is that after requesting all asynchronous
generators to be shutdown, the program should not execute code that
iterates over new asynchronous generators.
An example of how ``shutdown_asyncgens`` should be used::