➜

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 Peter.Saveliev
Recipients Peter.Saveliev, amaury.forgeotdarc, pitrou
Date 2011-08-13.07:01:36
SpamBayes Score 0.015231038
Marked as misclassified No
Message-id <1313218897.13.0.11139577833.issue11866@psf.upfronthosting.co.za>
In-reply-to
Content 
counter.next() is a C routine and it is atomic from Python's point of view — if I understand right.

The test shows that original threading.py leads to a (rare) race here, while with counter object there is no race condition.
History
Date User Action Args
2011-08-13 07:01:37Peter.Savelievsetrecipients: + Peter.Saveliev, amaury.forgeotdarc, pitrou
2011-08-13 07:01:37Peter.Savelievsetmessageid: <1313218897.13.0.11139577833.issue11866@psf.upfronthosting.co.za>
2011-08-13 07:01:36Peter.Savelievlinkissue11866 messages
2011-08-13 07:01:36Peter.Savelievcreate