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 pitrou
Recipients Albert.Strasheim, aljungberg, asksol, bquinlan, brian.curtin, gdb, gkcn, hongqn, jnoller, pitrou, vlasovskikh, vstinner
Date 2011-05-08.21:28:21
SpamBayes Score 4.650162e-07
Marked as misclassified No
Message-id <1304890103.08.0.698383464249.issue9205@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, here's a patch for the new approach.
CancelIoEx is loaded dynamically and, if unavailable, CancelIo is used instead. I take care to cancel or complete the I/O in the same method call where it is initiated, meaning there's no thread-specificity issues.

(of course, all this is a lot of code just to have the desired WaitForMultipleObjects() semantics on a named pipe. Thank you, Windows)
History
Date User Action Args
2011-05-08 21:28:25pitrousetrecipients: + pitrou, bquinlan, vstinner, jnoller, hongqn, brian.curtin, asksol, vlasovskikh, gdb, Albert.Strasheim, aljungberg, gkcn
2011-05-08 21:28:23pitrousetmessageid: <1304890103.08.0.698383464249.issue9205@psf.upfronthosting.co.za>
2011-05-08 21:28:22pitroulinkissue9205 messages
2011-05-08 21:28:22pitroucreate