Author neologix
Recipients asksol, jnoller, meador.inge, neologix, sbt, vilnis.termanis
Date 2011-10-06.20:20:39
SpamBayes Score 1.36971e-09
Marked as misclassified No
Message-id <1317932440.44.0.44932267518.issue8037@psf.upfronthosting.co.za>
In-reply-to
Content
> Modifying an object which is already on a traditional queue can also
> change what is received by the other thread (depending on timing). 
> So Queue.Queue's put() is not "atomic" either.  Therefore I do not
> believe this behaviour is a bug.

Agreed.

> However the solution proposed is a good one since it fixes Issue
> 10886.  In addition it prevents arbitrary code being run in the
> background thread by weakref callbacks or __del__ methods.  Such
> arbitrary code may cause inconsistent state in a forked process if
> the fork happens while the queue's thread is running -- see issue
> 6271.
[...]
> I would suggest closing this issue and letting Issue 10886 take it's
> place.

Makes sense.
History
Date User Action Args
2011-10-06 20:20:40neologixsetrecipients: + neologix, jnoller, asksol, meador.inge, vilnis.termanis, sbt
2011-10-06 20:20:40neologixsetmessageid: <1317932440.44.0.44932267518.issue8037@psf.upfronthosting.co.za>
2011-10-06 20:20:39neologixlinkissue8037 messages
2011-10-06 20:20:39neologixcreate