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:42:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1338597720.88.0.000987280153686.issue6721@psf.upfronthosting.co.za>
In-reply-to
Content
A slightly more ambitious solution than crashing / deadlocking always is to have Python automatically spawn a "fork server" whenever you start using threads.

Then, you would be able to have "subprocess" work cleanly, and not worry about any of this stuff.

I don't know if we want to take the perf hit on "import threading" though...
History
Date User Action Args
2012-06-02 00:42:00leshasetrecipients: + lesha, gregory.p.smith, vinay.sajip, jcea, pitrou, vstinner, nirai, bobbyi, neologix, Giovanni.Bajo, sdaoden, sbt, avian
2012-06-02 00:42:00leshasetmessageid: <1338597720.88.0.000987280153686.issue6721@psf.upfronthosting.co.za>
2012-06-02 00:42:00leshalinkissue6721 messages
2012-06-02 00:42:00leshacreate