-
-
Notifications
You must be signed in to change notification settings - Fork 33.9k
bpo-34687: asynico uses ProactorEventLoop by default #9538
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.
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
Conversation
On Windows, asyncio now uses ProactorEventLoop, instead of SelectorEventLoop.
Doc/library/asyncio-platforms.rst
Outdated
| Windows | ||
| ======= | ||
|
|
||
| The default event loop on Windows is :class:`ProactorEventLoop`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just put one .. versionchanged:: 3.8 here, there's no point in covering this info twice in this section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Doc/library/asyncio-platforms.rst
Outdated
| asyncio.run(your_code()) | ||
| The default event loop :class:`ProactorEventLoop` supports subprocesses. | ||
|
|
||
| On Windows, :class:`SelectorEventLoop` does not support subprocesses. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On Windows, the default event loop :class:ProactorEventLoop supports subprocesses, whereas :class:SelectorEventLoop does not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
|
When you're done making the requested changes, leave the comment: |
|
I have made the requested changes; please review again. |
|
Thanks for making the requested changes! @1st1: please review the changes made to this pull request. |
| is configured to use the default policy automatically. | ||
|
|
||
|
|
||
| .. class:: WindowsSelectorEventLoopPolicy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, one more change... 5 lines above this line:
The default asyncio policy. Uses :class:`SelectorEventLoop`
on both Unix and Windows platforms.
There is no need to install the default policy manually. asyncio
is configured to use the default policy automatically.
please change it to
The default asyncio policy. Uses :class:`SelectorEventLoop`
on Unix and :class:`ProactorEventLoop` on Windows.
There is no need to install the default policy manually. asyncio
is configured to use the default policy automatically.
.. versionchanged:: 3.8
:class:`ProactorEventLoop` is now default on Windows.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
^^^ updated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
For Windows, for which it's now the default for in Python 3.8: https://bugs.python.org/issue34687 python/cpython#9538 python/cpython@6ea29c5 https://docs.python.org/3/whatsnew/3.8.html#asyncio
On Windows, asyncio now uses ProactorEventLoop, instead of
SelectorEventLoop, by default.
https://bugs.python.org/issue34687