Alexey Borzenkov wrote:
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*
On 10/13/06, Fredrik Lundh [EMAIL PROTECTED] wrote:
any reason you cannot just use the subprocess module instead, like
everyone else?
Oh! Wow! I just simply didn't know of its existance (I'm pretty much
new to python), and both distutils and SCons (I was looking inside
them because they are
Alexey Borzenkov wrote:
any reason you cannot just use the subprocess module instead, like
everyone else?
Oh! Wow! I just simply didn't know of its existance (I'm pretty much
new to python), and both distutils and SCons (I was looking inside
them because they are major build systems and
Alexey Borzenkov wrote:
Oh! Wow! I just simply didn't know of its existance (I'm pretty much
new to python), and both distutils and SCons (I was looking inside
them because they are major build systems and surely had to execute
compilers somehow), and upon seeing that each of them invented
Hi all,
I've been looking at python 2.5 today and what I notices is absense of
spawnvp with this comment in os.py:
# At the moment, Windows doesn't implement spawnvp[e],
# so it won't have spawnlp[e] either.
I'm wondering, why so? Searching MSDN I can see that these functions
are
On 10/12/06, Alexey Borzenkov [EMAIL PROTECTED] wrote:
At least when I did it with my copy, nt.spawnvp seems to work fine...
Hi everyone again. I've created patch for spawn*p*, as well as for
exec*p* against trunk, so that when possible it uses crt's execvp[e]
(defined via HAVE_EXECVP, if there
On Thu, Oct 12, 2006, Alexey Borzenkov wrote:
Should I submit it to sourceforge as a patch, or someone can review it as is?
Always submit patches; that guarantees your work won't get lost.
--
Aahz ([EMAIL PROTECTED]) * http://www.pythoncraft.com/
If you don't know what your
Alexey Borzenkov schrieb:
Should I submit it to sourceforge as a patch, or someone can review it as is?
Please consider also exposing _wspawnvp, depending on whether path
argument is a Unicode object or not. See PEP 277 for guidance.
Since this would go into 2.6, support for Windows 95 isn't
On 10/13/06, Martin v. Löwis [EMAIL PROTECTED] wrote:
Please consider also exposing _wspawnvp, depending on whether path
argument is a Unicode object or not. See PEP 277 for guidance.
Since this would go into 2.6, support for Windows 95 isn't mandatory.
Umm... do you mean that spawn*p* on
Forgot to include python-dev...
On 10/13/06, Martin v. Löwis [EMAIL PROTECTED] wrote:
Umm... do you mean that spawn*p* on python 2.5 is an absolute no?
Yes. No new features can be added to Python 2.5.x; Python 2.5 has
already been released.
Ugh... that's just not fair. Because of this there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 12, 2006, at 8:46 PM, Alexey Borzenkov wrote:
Ugh... that's just not fair. Because of this there will be no spawn*p*
in python for another two years. x_x
Correct, but don't let that stop you. That's what distutils and the
Cheeseshop are
[Alexey Borzenkov]
Umm... do you mean that spawn*p* on python 2.5 is an absolute no?
[Martin v. Löwis]
Yes. No new features can be added to Python 2.5.x; Python 2.5 has
already been released.
[Alexey Borzenkov]
Ugh... that's just not fair. Because of this there will be no spawn*p*
in python
Alexey Borzenkov schrieb:
On 10/13/06, Martin v. Löwis [EMAIL PROTECTED] wrote:
Umm... do you mean that spawn*p* on python 2.5 is an absolute no?
Yes. No new features can be added to Python 2.5.x; Python 2.5 has
already been released.
Ugh... that's just not fair. Because of this there will
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?
14 matches
Mail list logo
