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, ronaldoussoren
Date 2009-09-24.07:30:16
SpamBayes Score 2.4931462e-06
Marked as misclassified No
Message-id <4ABA566C.9010003@v.loewis.de>
In-reply-to <1253616536.4.0.145439176425.issue6834@psf.upfronthosting.co.za>
Content
> This version uses posix_spawn rather than execv to start the real 
> interpreter. 

In what way is that better? It creates a new process (IIUC); therefore,
I think that using it is worse than using execv. Anybody killing the
pythonw process would only kill the wrapper.

> The main advantage of the new implementation is that 'arch 
> -ppc pythonw' works as expected, with the current version of pythonw the 
> 'arch' command only affects the pythonw executable and not the real 
> interpreter.

I suppose this would also be possible through execv?
History
Date User Action Args
2009-09-24 07:30:18loewissetrecipients: + loewis, ronaldoussoren
2009-09-24 07:30:16loewislinkissue6834 messages
2009-09-24 07:30:16loewiscreate