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 eryksun, paul.moore, python-dev, rocco.matano, steve.dower, tim.golden, vstinner, zach.ware
Date 2015-09-15.08:34:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1442306056.21.0.296612392667.issue25118@psf.upfronthosting.co.za>
In-reply-to
Content
Oops :-/ Yet another Python 3.5.0 regression, it's now fixed.

os.waitpid() was not tested at all on Windows. os.waitpid() is not the best option to wait for a subprocess completion. By the way, you should use the subprocess module which is more portable, is widely used, etc. IMHO os.spawn*() is more kept for backward compatibility.

> It seems to me this entire loop should be removed. The Windows C runtime doesn't set errno to EINTR. In the case of _cwait it doesn't even use an alertable wait (i.e. it can't be interrupted by a regular asynchronous procedure call).

Well, it looks like you are right: _cwait() cannot be interrupted on Windows. But I chose to only fix the if() after the loop... just in case.
History
Date User Action Args
2015-09-15 08:34:16vstinnersetrecipients: + vstinner, paul.moore, tim.golden, python-dev, zach.ware, eryksun, steve.dower, rocco.matano
2015-09-15 08:34:16vstinnersetmessageid: <1442306056.21.0.296612392667.issue25118@psf.upfronthosting.co.za>
2015-09-15 08:34:16vstinnerlinkissue25118 messages
2015-09-15 08:34:15vstinnercreate