Message222570
| Author |
dhduvall |
| Recipients |
alex, benjamin.peterson, dhduvall, gennad, gregory.p.smith, neologix |
| Date |
2014年07月08日.17:23:56 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1404840236.74.0.304096857292.issue20104@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Our project (the Solaris packaging system, IPS), relies on posix_spawn() primarily for the ability to fork without making a large memory reservation (and possibly failing) because the forking process was itself very large. That's the (a?) bug benefit of posix_spawn() -- it's not a benefit for the programmer using it (who might have to fall back to fork/exec), but for the end-user that benefits from its streamlined operation.
You're right that it doesn't handle everything that subprocess.Popen() does -- though at least on Solaris there's a way to change the cwd in the file actions, and I'm sure we'd consider adding a way to do the setsid() as well. The rest should be possible cross-platform. |
|