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 sbt
Recipients sbt, techtonik
Date 2013-09-29.15:39:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1380469191.4.0.160231867501.issue19124@psf.upfronthosting.co.za>
In-reply-to
Content
As I wrote in http://bugs.python.org/issue19066, on Windows execv() is equivalent to

    os.spawnv(os.P_NOWAIT, ...)
    os._exit(0)

This means that control is returned to cmd when the child process *starts* (and afterwards you have cmd and the child connected to the same console).

On Unix control is returned to the shell only once the child process *ends*.

Although it might be less memory efficient, you would actually get something closer to Unix behaviour by replacing os.execv(...) with

    sts = os.spawnv(os.P_WAIT, ...)
    _exit(sts)

or

    sts = subprocess.call(...)
    _exit(sts)

This is why I said that execv() is useless on Windows and that you should just use subprocess instead.
History
Date User Action Args
2013-09-29 15:39:51sbtsetrecipients: + sbt, techtonik
2013-09-29 15:39:51sbtsetmessageid: <1380469191.4.0.160231867501.issue19124@psf.upfronthosting.co.za>
2013-09-29 15:39:51sbtlinkissue19124 messages
2013-09-29 15:39:51sbtcreate