[Python-Dev] Why spawnvp not implemented on Windows?

Anthony Baxter anthony at interlink.com.au
Fri Oct 13 07:11:21 CEST 2006

On Friday 13 October 2006 10:46, Alexey Borzenkov wrote:
> But the fact that I have to use similar code anywhere I need to use
> spawnlp is not fair. Notice that _spawnvpe is simply a clone of
> _execvpe from os.py, maybe if the problem is new API in c source, this
> approach could be used in os.py?

Oddly, "fair" isn't a constraint in PEP-0006. Backwards and forwards 
compatibility between all point releases in a major release is. Adding it to 
os.py rather than C code doesn't make a difference.

> P.S. Although it's a bit stretching, one might also say that
> implementing spawn*p* on windows is not actually a new feature, and
> rather is a bugfix for misfeature. Why every other platform can
> benefit from spawn*p* and only Windows can't? This just makes
> os.spawn*p* useless: it becomes unreliable and can't be used in
> portable code at all.

"One" might say that. I wouldn't. It stays out until 2.6.


Anthony Baxter     <anthony at interlink.com.au>
It's never too late to have a happy childhood.

More information about the Python-Dev mailing list