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 loewis
Recipients loewis, mhammond, python-dev, sbt, vstinner
Date 2011-11-09.20:53:36
SpamBayes Score 1.8728266e-06
Marked as misclassified No
Message-id <4EBAE846.4050405@v.loewis.de>
In-reply-to <1320853875.11.0.548269501088.issue13374@psf.upfronthosting.co.za>
Content
> Probably os.execv() should be implemented on Windows with _wexecv()
> instead of _execv().  Likewise for other functions which have "wide"
> versions.  Or maybe it wouldn't be worth the effort, since it would
> mean writing separate Windows implementations.

Writing separate Windows versions has a long tradition in posixmodule.c,
so in principle it's fine. It still may not be worth the effort since
the function is deprecated in favor of the subprocess module. However,
if code was contributed in that direction, we would likely accept it.
History
Date User Action Args
2011-11-09 20:53:37loewissetrecipients: + loewis, mhammond, vstinner, python-dev, sbt
2011-11-09 20:53:37loewislinkissue13374 messages
2011-11-09 20:53:36loewiscreate