Skip to content

bpo-34679: Restore instantiation Windows IOCP event loop from non-main thread #15492

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

Merged
merged 4 commits into from
Aug 26, 2019

Conversation

asvetlov
Copy link
Contributor

@asvetlov asvetlov commented Aug 25, 2019

@asvetlov asvetlov requested a review from 1st1 as a code owner August 25, 2019 15:12
@asvetlov asvetlov changed the title bpo-34769: Restore instantiation Windows IOCP event loop from non-main thread bpo-34679: Restore instantiation Windows IOCP event loop from non-main thread Aug 25, 2019
Copy link
Contributor

@aeros aeros left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR @asvetlov, I think this PR is more extensive than the initial one I created (#15477, just included the bug fix), so I closed mine.

I have a few minor suggestions:

thread = threading.Thread(target=func)
thread.start()
thread.join()
self.assertTrue(finished)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea with regards to adding tests to ensure that further optimizations/changes don't accidentally recreate the bug.

@aeros aeros added type-bug An unexpected behavior, bug, or error OS-windows labels Aug 25, 2019
Copy link
Member

@gvanrossum gvanrossum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please change the news file per suggestion from @aeros167 (I wasn't able to commit it).

@asvetlov
Copy link
Contributor Author

@gvanrossum @aeros167 thanks the review.
All notes are fixed.

@asvetlov asvetlov merged commit 1c06009 into python:master Aug 26, 2019
@asvetlov asvetlov deleted the proactor-nonmain-thread branch August 26, 2019 09:51
@bedevere-bot
Copy link

@asvetlov: Please replace # with GH- in the commit message next time. Thanks!

@miss-islington
Copy link
Contributor

Thanks @asvetlov for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8.
🐍🍒⛏🤖

@bedevere-bot
Copy link

GH-15512 is a backport of this pull request to the 3.8 branch.

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Aug 26, 2019
…n thread (pythonGH-15492)

* Restore running proactor event loop from non-main thread

Co-Authored-By: Kyle Stanley <[email protected]>
(cherry picked from commit 1c06009)

Co-authored-by: Andrew Svetlov <[email protected]>
miss-islington added a commit that referenced this pull request Aug 26, 2019
…n thread (GH-15492)

* Restore running proactor event loop from non-main thread

Co-Authored-By: Kyle Stanley <[email protected]>
(cherry picked from commit 1c06009)

Co-authored-by: Andrew Svetlov <[email protected]>
lisroach pushed a commit to lisroach/cpython that referenced this pull request Sep 10, 2019
…n thread (python#15492)

* Restore running proactor event loop from non-main thread

Co-Authored-By: Kyle Stanley <[email protected]>
DinoV pushed a commit to DinoV/cpython that referenced this pull request Jan 14, 2020
…n thread (python#15492)

* Restore running proactor event loop from non-main thread

Co-Authored-By: Kyle Stanley <[email protected]>
websurfer5 pushed a commit to websurfer5/cpython that referenced this pull request Jul 20, 2020
…n thread (python#15492)

* Restore running proactor event loop from non-main thread

Co-Authored-By: Kyle Stanley <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OS-windows type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants