Author vstinner
Recipients gvanrossum, loewis, pitrou, sbt, vstinner
Date 2014-01-28.08:50:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390899023.73.0.487594884753.issue20414@psf.upfronthosting.co.za>
In-reply-to
Content
> I did intend to switch multiprocessing over to using _overlapped
> but I did not get round to it.

Do you mean that _overlapped module is newer and should be used instead of _winapi? If multiprocssing is patched to use _overlapped, we can drop overlapped code from _winapi, should we keep functions like WriteFile() without overlapped support? (I think that we should keep these functions, it was discussed to support the native Windows API for files.)

IMO such change can be done in Python 3.5, it is risky and can wait.

But until that, I'm concerned by overlapped deallocator which is different in the two modules. Attached fixes _overlapped module to use the same logic than _winapi: give up on Windows XP during Python finalization if the overlapped is still pending, don't deallocate memory, exit immediatly. See issue #19565 for the rationale of this change.
History
Date User Action Args
2014-01-28 08:50:23vstinnersetrecipients: + vstinner, gvanrossum, loewis, pitrou, sbt
2014-01-28 08:50:23vstinnersetmessageid: <1390899023.73.0.487594884753.issue20414@psf.upfronthosting.co.za>
2014-01-28 08:50:23vstinnerlinkissue20414 messages
2014-01-28 08:50:23vstinnercreate