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 donmez, jnoller, mark.dickinson, pitrou
Date 2008-08-18.19:50:34
SpamBayes Score 2.268517e-06
Marked as misclassified No
Message-id <1219089032.5624.18.camel@fsol>
In-reply-to <1219088543.86.0.0652188855417.issue3578@psf.upfronthosting.co.za>
Content
Le lundi 18 août 2008 à 19:42 +0000, Ismail Donmez a écrit :
> Ismail Donmez <ismail@namtrac.org> added the comment:
> 
> Ah cool, we might be at the end of multiprocessing problems then I guess 
> :-)

Well, not really, it should be diagnosed why the dictionary mutates in
the first place. This dictionary is apparently processed in a child
process just after a fork() occurred, so logically there shouldn't be
several threads running.
Unless processing the dictionary itself can create some new threads?
History
Date User Action Args
2008-08-18 19:50:36pitrousetrecipients: + pitrou, mark.dickinson, donmez, jnoller
2008-08-18 19:50:35pitroulinkissue3578 messages
2008-08-18 19:50:34pitroucreate