[issue15005] corrupted contents of stdout result from subprocess call under a trace

anatoly techtonik added the comment: And how to find all such issues for Python 2 that people need to be aware of in this tracker? -- ___ Python tracker ___

[issue15005] corrupted contents of stdout result from subprocess call under a trace

Amaury Forgeot d'Arc added the comment: So the issue can be closed: - subprocess was rewritten in C on Python3 for good reasons: it's wrong (and dangerous) to run Python code between fork() and exec(); this bug report is another example. - This change is too large to be merged to 2.7. - Ther

[issue15005] corrupted contents of stdout result from subprocess call under a trace

anatoly techtonik added the comment: Python 3 is not affected. Python 2.7, Linux only. -- ___ Python tracker ___ ___ Python-bugs-list

[issue15005] corrupted contents of stdout result from subprocess call under a trace

anatoly techtonik added the comment: I can not repeat this neither on Python 2.7 nor on Python 3 on Windows Vista. Need to run this on a Linux system to confirm. -- ___ Python tracker _

[issue15005] corrupted contents of stdout result from subprocess call under a trace

Amaury Forgeot d'Arc added the comment: So, does this page report an issue with Python2, or Python3? -- ___ Python tracker ___ ___ Pyt

[issue15005] corrupted contents of stdout result from subprocess call under a trace

anatoly techtonik added the comment: I can't repeat this on Windows. Looks like it is a Linux issue, because of forks. -- ___ Python tracker ___

[issue15005] corrupted contents of stdout result from subprocess call under a trace

Changes by anatoly techtonik : -- title: corrupted output from subprocess call under a trace -> corrupted contents of stdout result from subprocess call under a trace ___ Python tracker ___