➜

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 gvanrossum
Recipients anonymous2017, gvanrossum, yselivanov
Date 2017-01-17.23:27:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1484695674.29.0.270618350866.issue29303@psf.upfronthosting.co.za>
In-reply-to
Content 
Locks are not meant to have predictable behavior like that. They are meant to protect against concurrent access. If you want fairness you have to look elsewhere.
History
Date User Action Args
2017-01-17 23:27:54gvanrossumsetrecipients: + gvanrossum, yselivanov, anonymous2017
2017-01-17 23:27:54gvanrossumsetmessageid: <1484695674.29.0.270618350866.issue29303@psf.upfronthosting.co.za>
2017-01-17 23:27:54gvanrossumlinkissue29303 messages
2017-01-17 23:27:54gvanrossumcreate