summaryrefslogtreecommitdiffstats
path: root/Python/sysmodule.c
diff options
context:
space:
mode:
authorGregory P. Smith <greg@krypto.org>2017-09-05 18:20:02 (GMT)
committerGitHub <noreply@github.com>2017-09-05 18:20:02 (GMT)
commit5e8e371364ee58dadb9a4e4e51c7e9cf6bedbfae (patch)
treead244d74a8a78950a508a59cf3afd2b7952a549e /Python/sysmodule.c
parent9721e51daf59e9a2f56dbf7c2428ea79c0b13be0 (diff)
downloadcpython-5e8e371364ee58dadb9a4e4e51c7e9cf6bedbfae.zip
cpython-5e8e371364ee58dadb9a4e4e51c7e9cf6bedbfae.tar.gz
cpython-5e8e371364ee58dadb9a4e4e51c7e9cf6bedbfae.tar.bz2
bpo-27448: Work around a gc.disable race condition in subprocess. (#1932)
* bpo-27448: Work around a gc.disable race condition in subprocess. This works around a gc.isenabled/gc.disable race condition in the 2.7 subprocess module by using a lock for the critical section. It'll prevent multiple simultaneous subprocess launches from winding up with gc remaining disabled but it can't fix the ultimate problem: gc enable and disable is a global setting and a hack. Users are *strongly encouraged* to use subprocess32 from PyPI instead of the 2.7 standard library subprocess module. Mixing threads with subprocess is a recipie for disaster otherwise even with "fixes" to ameliorate common issues like this. * Add a blurb!
Diffstat (limited to 'Python/sysmodule.c')
0 files changed, 0 insertions, 0 deletions