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 njs
Recipients giampaolo.rodola, njs, vstinner
Date 2019-11-06.00:35:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
You can't solve a time-of-check-to-time-of-use race by adding another check. I guess your patch might narrow the race window slightly, but it was a tiny window before and it's a tiny window after, so I don't really get it.

The test doesn't demonstrate a race condition. What it demonstrates is increased robustness against user code that corrupts Popen's internal state by reaping one of its processes behind its back.

That kind of robustness might be a good motivation on its own! (I actually just did a bunch of work to make trio more robust against user code closing fds behind its back, which is a similar kind of thing.) But it's a very different motivation than what you say in this bug.
Date User Action Args
2019-11-06 00:35:37njssetrecipients: + njs, vstinner, giampaolo.rodola
2019-11-06 00:35:37njssetmessageid: <>
2019-11-06 00:35:37njslinkissue38630 messages
2019-11-06 00:35:37njscreate