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 pitrou
Recipients Giovanni.Bajo, avian, bobbyi, gregory.p.smith, neologix, nirai, pitrou, sdaoden, vstinner
Date 2011-06-30.15:08:49
SpamBayes Score 1.86346e-06
Marked as misclassified No
Message-id <1309446488.3214.6.camel@localhost.localdomain>
In-reply-to <>
> 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.
Date User Action Args
2011-06-30 15:08:49pitrousetrecipients: + pitrou, gregory.p.smith, vstinner, nirai, bobbyi, neologix, Giovanni.Bajo, sdaoden, avian
2011-06-30 15:08:49pitroulinkissue6721 messages
2011-06-30 15:08:49pitroucreate