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 lesha
Recipients Giovanni.Bajo, avian, bobbyi, gregory.p.smith, jcea, lesha, neologix, nirai, pitrou, sbt, sdaoden, vinay.sajip, vstinner
Date 2012-06-02.00:54:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Actually, we might be able to automatically spawn a safe fork server _only_ when people start mixing threading and subprocess.

I'm not totally sure if this would allow us to salvage multiprocessing as well...

The tricky bit is that we'd need to proxy into the fork server all the calls having to do with file descriptors / sockets that we would want to pass into the child processes.

That suggests to me that it'll be really hard to do this in a backwards-compatible way.

Given that subprocess is a pretty broken library, this might be a good time to replace it anyway.
Date User Action Args
2012-06-02 00:55:00leshasetrecipients: + lesha, gregory.p.smith, vinay.sajip, jcea, pitrou, vstinner, nirai, bobbyi, neologix, Giovanni.Bajo, sdaoden, sbt, avian
2012-06-02 00:55:00leshasetmessageid: <>
2012-06-02 00:54:59leshalinkissue6721 messages
2012-06-02 00:54:59leshacreate