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. Sorry Anthony -- Anthony Baxter <[EMAIL PROTECTED]> It's never too late to have a happy childhood. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
