| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…w loop. Original patch by Dan O'Reilly.
|
I think it would be nice if the test did a bit more, for example run some coroutine or perhaps even some simple socket ping-pong. That would check that other infrastructure is also fork-safe, not just the event loop instantiation logic. |
Sorry, something went wrong.
|
Sure, added a basic test for that. Don't think we need more than that though, as the entirety of "other infrastructure" should be initialized via the loop's constructor. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. I'm assuming the test isn't run on Windows?
Sorry, something went wrong.
Yes, it's only for Unix. |
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm
Sorry, something went wrong.
|
Thanks @1st1 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6, 3.7. |
Sorry, something went wrong.
|
GH-7215 is a backport of this pull request to the 3.7 branch. |
Sorry, something went wrong.
Original patch by Dan O'Reilly. (cherry picked from commit 5d97b7b) Co-authored-by: Yury Selivanov <yury@magic.io>
|
Sorry, @1st1, I could not cleanly backport this to 3.6 due to a conflict. |
Sorry, something went wrong.
|
GH-7218 is a backport of this pull request to the 3.6 branch. |
Sorry, something went wrong.
Original patch by Dan O'Reilly.
| Back | FazBrowse Home | New Git URL |
Original patch by Dan O'Reilly.
https://bugs.python.org/issue22087