A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2003-April/034473.html below:

[Python-Dev] Why is spawn*p* not available on Windows?

[Python-Dev] Why is spawn*p* not available on Windows?Shane Holloway (IEEE) shane.holloway@ieee.org
Thu, 10 Apr 2003 13:47:46 -0600
Ok, so here's my story.  I got curious as to why the various spawn*p* 
were not available on Windows.  The conclusion I came to is that only 
"spawnv" and "spawnve" are exported by posixmodule.c, and os.py creates 
the other variants in terms of these functions.  However, the "spawnvp" 
and "spawnvpe" python implementations are dependant upon the availablity 
of "fork".

So, after all that, I looked in standard library header file for 
process.h and found function prototypes for the various _spawn 
functions.  Would it make sense to add support for "spawnvp" and 
"spawnvpe" to posixmodule.c?  Should it be guarded by the existing 
HAVE_SPAWNV, new HAVE_SPAWNVP, or by MS_WINDOWS definitions?

Or, has someone already tried this with lessons learned? 

Thanks,
-Shane




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4