mirror of
https://github.com/python/cpython.git
synced 2025-11-01 18:51:43 +00:00
Tulip issue 83, Python issue #21252: Fill some XXX docstrings in asyncio
This commit is contained in:
parent
1a170a74f7
commit
f9e49dd346
3 changed files with 29 additions and 18 deletions
|
|
@ -64,19 +64,19 @@ An event loop policy must implement the following interface:
|
|||
|
||||
.. method:: get_event_loop()
|
||||
|
||||
Get the event loop for current context. Returns an event loop object
|
||||
implementing :class:`BaseEventLoop` interface, or raises an exception in case
|
||||
Get the event loop for the current context. Returns an event loop object
|
||||
implementing the :class:`BaseEventLoop` interface, or raises an exception in case
|
||||
no event loop has been set for the current context and the current policy
|
||||
does not specify to create one. It should never return ``None``.
|
||||
|
||||
.. method:: set_event_loop(loop)
|
||||
|
||||
Set the event loop of the current context to *loop*.
|
||||
Set the event loop for the current context to *loop*.
|
||||
|
||||
.. method:: new_event_loop()
|
||||
|
||||
Create and return a new event loop object according to this policy's rules.
|
||||
If there's need to set this loop as the event loop of the current context,
|
||||
If there's need to set this loop as the event loop for the current context,
|
||||
:meth:`set_event_loop` must be called explicitly.
|
||||
|
||||
Access to the global loop policy
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue