-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
bpo-41217: Fix incorrect note in the asyncio.create_subprocess_shell() docs #21360
bpo-41217: Fix incorrect note in the asyncio.create_subprocess_shell() docs #21360
Conversation
…) docs On Windows, the default asyncio event loop is ProactorEventLoop (as of 3.8).
This is a "skip news" PR. |
Thanks @ZackerySpytz for the PR, and @zooba for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8, 3.9. |
…) docs (pythonGH-21360) On Windows, the default asyncio event loop is ProactorEventLoop (as of 3.8). (cherry picked from commit 4dfb190) Co-authored-by: Zackery Spytz <zspytz@gmail.com>
GH-22792 is a backport of this pull request to the 3.9 branch. |
…) docs (pythonGH-21360) On Windows, the default asyncio event loop is ProactorEventLoop (as of 3.8). (cherry picked from commit 4dfb190) Co-authored-by: Zackery Spytz <zspytz@gmail.com>
GH-22793 is a backport of this pull request to the 3.8 branch. |
…) docs (pythonGH-21360) On Windows, the default asyncio event loop is ProactorEventLoop (as of 3.8).
You guys missed a copy of the same note at a different location here: It's still visible in all versions of the documentation for Python >=3.8 and should be fixed as well, as I (e.g.) got confused by it! :) |
On Windows, the default asyncio event loop is ProactorEventLoop (as
of 3.8).
https://bugs.python.org/issue41217