Gregory P. Smith <g...@krypto.org> added the comment:
As a note on the general pattern, a user at work diagnosed a ^C problem in
their code when running on 2.7 to be due to Queue.get's
acquire()
try:
...
finally:
release()
Pattern, with the KeyboardInterrupt triggering after acquire() but before the
try is entered. so release() is never called.
A try finally pattern that probably alleviates this by entering the try block
first might look like:
try:
acquire()
...
finally:
try:
release()
except ThreadError:
pass # interrupted before acquire() succeeded.
It'd be a shame if any with statements lock acquisition context managers need
to be turned into that, but I _believe_ it'd be a viable workaround for the
time being if this race is found to be biting anyone.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue29988>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
