Author vilnis.termanis
Recipients jnoller, meador.inge, vilnis.termanis
Date 2010-03-02.16:38:45
SpamBayes Score 5.78215e-06
Marked as misclassified No
Message-id <>
I couldn't see the wood for the trees:
If put() is thread-blocking, multiprocessing.Queue is reduced to the same functionality as multiprocessing.queues.SimpleQueue, if I'm not mistaken. So maybe there should be a warning in the documentation that, for multiprocessing.[Joinable]Queue, modifying obj straight after calling put(obj) might en-queue the modified version.

To me at least this wasn't obvious until I looked at the multiprocessing.queue code.

I've modified the example for clarity and retracted the (unworthy) patch attempt.

Date User Action Args
2010-03-02 16:38:47vilnis.termanissetrecipients: + vilnis.termanis, jnoller, meador.inge
2010-03-02 16:38:47vilnis.termanissetmessageid: <>
2010-03-02 16:38:46vilnis.termanislinkissue8037 messages
2010-03-02 16:38:45vilnis.termaniscreate