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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, techtonik
Date 2012-06-05.15:06:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1338908784.79.0.322964436966.issue15005@psf.upfronthosting.co.za>
In-reply-to
Content
Python2 has a pure python implementation of subprocess, with separate calls to fork() and exec(); so the output of the subprocess contains the trace of the forked Python interpreter, until the exec() system call.
Python3 has a C implementation: _posixsubprocess.fork_exec() won't call the Python interpreter between fork() and exec(), and no trace is emitted.

Yes, Python3 is better :)
History
Date User Action Args
2012-06-05 15:06:24amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, techtonik
2012-06-05 15:06:24amaury.forgeotdarcsetmessageid: <1338908784.79.0.322964436966.issue15005@psf.upfronthosting.co.za>
2012-06-05 15:06:24amaury.forgeotdarclinkissue15005 messages
2012-06-05 15:06:24amaury.forgeotdarccreate