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 | eryksun |
|---|---|
| Recipients | Grissiom.Gu, cvrebert, docs@python, eryksun, gjb1002, loewis, sbt, scopatz, terry.reedy |
| Date | 2017年02月04日.00:16:42 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1486167402.35.0.220182704154.issue15451@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> difference from the behaviour of Posix's execvpe() was deliberate POSIX doesn't define execvpe [1]. GNU glibc implemented it in 2009 [2]. On Windows, MSC has had execvpe and spawnvpe since at least 5.0 [3], and I think it arrived in 4.0 in 1986. Guido added os._execvpe in 1.2b4 [4] in 1995. I think it's the only implementation of execvpe that searches the passed environment. [1]: http://pubs.opengroup.org/onlinepubs/9699919799/functions/execvp.html [2]: https://sourceware.org/ml/libc-alpha/2009-10/msg00063.html [3]: https://openlibrary.org/works/OL2028669W [4]: https://hg.python.org/cpython/file/534a97c400cc/Lib/os.py |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017年02月04日 00:16:42 | eryksun | set | recipients: + eryksun, loewis, terry.reedy, gjb1002, cvrebert, docs@python, sbt, Grissiom.Gu, scopatz |
| 2017年02月04日 00:16:42 | eryksun | set | messageid: <1486167402.35.0.220182704154.issue15451@psf.upfronthosting.co.za> |
| 2017年02月04日 00:16:42 | eryksun | link | issue15451 messages |
| 2017年02月04日 00:16:42 | eryksun | create | |