Message227095
On Windows, write
a.py:
import subprocess
def ccall(cmdline, stdout, stderr):
proc = subprocess.Popen(['python', 'b.py'], stdout=subprocess.PIPE, stderr=subprocess.PIPE)
proc.communicate()
if proc.returncode != 0: raise subprocess.CalledProcessError(proc.returncode, cmdline)
return 0
# To fix subprocess.check_call, uncomment the following, which is functionally equivalent:
# subprocess.check_call = ccall
subprocess.check_call(['python', 'b.py'], stdout=subprocess.PIPE, stderr=subprocess.PIPE)
print 'Finished!'
Then write b.py:
import sys
str = 'aaa'
for i in range(0,16): str = str + str
for i in range(0,2): print >> sys.stderr, str
for i in range(0,2): print str
Finally, run 'python a.py'. The application will hang. Uncomment the specicied line to fix the execution.
This is a documented failure on the python subprocess page, but why not just fix it up directly in python itself?
One can think that modifying stdout or stderr is not the intent for subprocess.check_call, but python certainly should not hang because of that. |
|
Date |
User |
Action |
Args |
2014-09-19 13:56:39 | juj | set | recipients:
+ juj |
2014-09-19 13:56:39 | juj | set | messageid: <1411134999.3.0.739689982343.issue22442@psf.upfronthosting.co.za> |
2014-09-19 13:56:39 | juj | link | issue22442 messages |
2014-09-19 13:56:38 | juj | create | |
|