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 techtonik
Recipients loewis, sbt, techtonik, terry.reedy
Date 2013-09-29.11:18:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAPkN8xJecbMSyK0Z1vz7ASk3_Tuhd38p6YBVeBdFgpjeu0vfcw@mail.gmail.com>
In-reply-to <1380452717.22.0.825106716954.issue19066@psf.upfronthosting.co.za>
Content
On Sun, Sep 29, 2013 at 2:05 PM, Richard Oudkerk <report@bugs.python.org> wrote:
> See  http://bugs.python.org/issue436259

I am not sure that I should see there. There is discussion of DOS,
which is not supported, also some complain about Windows execv
function, which deprecated since VC++ 2005 (which I hope also not
supported). Can you be more specific?

> This is a problem with Window's implementation of spawn*() and exec*().

> Note that on Windows exec*() is useless: it just starts a subprocess and exits the current process.  You can use subprocess to get the same effect.

Are you describing Windows implementation of _exec()
http://msdn.microsoft.com/en-us/library/431x4c1w.aspx or current
Python implementation?

> Just use subprocess instead which gets this stuff right.

subprocess doesn't replace os.exec*, see issue19060
History
Date User Action Args
2013-09-29 11:18:26techtoniksetrecipients: + techtonik, loewis, terry.reedy, sbt
2013-09-29 11:18:26techtoniklinkissue19066 messages
2013-09-29 11:18:26techtonikcreate