Message139488
| Author |
pitrou |
| Recipients |
Giovanni.Bajo, avian, bobbyi, gregory.p.smith, neologix, nirai, pitrou, sdaoden, vstinner |
| Date |
2011年06月30日.15:08:49 |
| SpamBayes Score |
1.8634641e-06 |
| Marked as misclassified |
No |
| Message-id |
<1309446488.3214.6.camel@localhost.localdomain> |
| In-reply-to |
<1309446248.54.0.197690969309.issue6721@psf.upfronthosting.co.za> |
| Content |
> I was thinking about a run time warning that is emitted if you call
> os.fork() while multiple threads are active. It is ugly, but at least
> it tells you you are doing something that will in most cases not work
> correctly.
The problem is that multiprocessing itself, by construction, uses fork()
with multiple threads. Perhaps there's a way to use only non-blocking
communication instead (rendering the helper threads useless), but that's
not a trivial change. |
|