You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/gpshead'closed_at=<Date2014-04-23.08:35:30.727>created_at=<Date2014-04-17.21:49:43.112>labels= ['type-bug']
title='subprocess Popen objects are not thread safe w.r.t. wait() and returncode being set'updated_at=<Date2014-04-23.08:35:30.725>user='https://github.com/gpshead'
At first glance it appears that the .returncode attribute is not safely set after the wait call... This test code is using the Popen object from multiple threads at once.
Attaching a proposed fix for this issue. It should make the wait() and poll() methods thread safe. I need to turn the reproducer code into an actual test case and add more test cases for coverage of all code paths being touched.
I haven't examined the windows side of this code for the issue, it may also be useful there.
New changeset df45d0336dad by Gregory P. Smith in branch 'default':
subprocess's Popen.wait() is now thread safe so that multiple threads http://hg.python.org/cpython/rev/df45d0336dad
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: