➜

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 vilnis.termanis
Recipients vilnis.termanis
Date 2010-03-01.22:28:31
SpamBayes Score 4.9349413e-13
Marked as misclassified No
Message-id <1267482513.63.0.958385550471.issue8037@psf.upfronthosting.co.za>
In-reply-to
Content 
More notes:
- Reason for non-atmoic behaviour is due to queue _feeder thread sending the object after the put() method has already exited. Hence changing the object straight after put() can result in the modified object being sent instead.
- Reproduced under Win32 and Ubuntu-64 with v2.6.4
- Not tried with v3.* but looking at the ToT code
  it might also be affected
- The attached patch makes put() atomic but I am completely unsure about whether this is the correct way to address the problem (if it's seen as one).

Regards,
VT
History
Date User Action Args
2010-03-01 22:28:33vilnis.termanissetrecipients: + vilnis.termanis
2010-03-01 22:28:33vilnis.termanissetmessageid: <1267482513.63.0.958385550471.issue8037@psf.upfronthosting.co.za>
2010-03-01 22:28:32vilnis.termanislinkissue8037 messages
2010-03-01 22:28:31vilnis.termaniscreate