Message 234448 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	vstinner
Recipients	gvanrossum, steve.dower, tim.golden, vstinner, yselivanov, zach.ware
Date	2015-01-21.22:32:53
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1421879573.47.0.0852926503812.issue23293@psf.upfronthosting.co.za>
In-reply-to

Content
Currently, IocpProactor.connect_pipe() is implemented with QueueUserWorkItem() which starts a thread that cannot be interrupted. Because of that, this function requires special cases in _register() and close() methods of IocpProactor. While fixing the issue #23095, I saw that IocpProactor.connect_pipe() causes "GetQueuedCompletionStatus() returned an unexpected event" messages to be logged, but also to hang the test suite. I propose a solution to reimplement IocpProactor.connect_pipe() without a thread: https://code.google.com/p/tulip/issues/detail?id=197 It should fix this issue.

Currently, IocpProactor.connect_pipe() is implemented with QueueUserWorkItem() which starts a thread that cannot be interrupted. Because of that, this function requires special cases in _register() and close() methods of IocpProactor.

While fixing the issue #23095, I saw that IocpProactor.connect_pipe() causes "GetQueuedCompletionStatus() returned an unexpected event" messages to be logged, but also to hang the test suite.

I propose a solution to reimplement IocpProactor.connect_pipe() without a thread:
https://code.google.com/p/tulip/issues/detail?id=197

It should fix this issue.

History
Date	User	Action	Args
2015-01-21 22:32:53	vstinner	set	recipients: + vstinner, gvanrossum, tim.golden, zach.ware, yselivanov, steve.dower
2015-01-21 22:32:53	vstinner	set	messageid: <1421879573.47.0.0852926503812.issue23293@psf.upfronthosting.co.za>
2015-01-21 22:32:53	vstinner	link	issue23293 messages
2015-01-21 22:32:53	vstinner	create