Skip to content

[3.11] gh-100160: Tweak the documentation for the default asyncio policy #100969

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 13, 2023
Merged

[3.11] gh-100160: Tweak the documentation for the default asyncio policy #100969

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
696f060
gh-100160: Tweak the documentation for the default asyncio policy
serhiy-storchaka Jan 12, 2023
3f10ab1
Merge branch '3.11' into asyncio-default-policy-docs-3.11
serhiy-storchaka Jan 13, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions Doc/library/asyncio-policy.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,9 +113,9 @@ asyncio ships with the following built-in policies:
On Windows, :class:`ProactorEventLoop` is now used by default.

.. note::
In Python versions 3.10.9, 3.11.1 and 3.12 this function emits a
:exc:`DeprecationWarning` if there is no running event loop and no
current loop is set.
In Python versions 3.10.9, 3.11.1 and 3.12 the :meth:`get_event_loop`
method of the default asyncio policy emits a :exc:`DeprecationWarning`
if there is no running event loop and no current loop is set.
In some future Python release this will become an error.


Expand Down