A lock that prioritizes acquire()s?
David M Chess
chess at us.ibm.com
Wed Oct 24 18:04:15 EDT 2012
More information about the Python-list mailing list
Wed Oct 24 18:04:15 EDT 2012
- Previous message (by thread): A lock that prioritizes acquire()s?
- Next message (by thread): Listen for changes in variable (alsaaudio.Mixer(x,x).getvolume(x)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lovely, thanks for the ideas! I remember considering having release() pick the next thread to notify, where all the waiters were sitting on separate Conditions or whatever; not sure why I didn't pursue it to the end. Probably distracted by something shiny; or insufficient brainpower. :) DC -- -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-list/attachments/20121024/9b4fa1a8/attachment.html>
- Previous message (by thread): A lock that prioritizes acquire()s?
- Next message (by thread): Listen for changes in variable (alsaaudio.Mixer(x,x).getvolume(x)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list