Guido van Rossum added the comment: This (and the other issue you mention) is because the regular acquire() method on a basic lock cannot be interrupted. That's unlikely to go away, so you'll just have to live with this. As you've discovered, specifying a timeout solves the issue. Since code running in threads doesn't receive signals anyway (in Python), it would be fairly pointless to slow down lock acquisition in order to support keyboard interrupts.
---------- nosy: +gvanrossum resolution: -> wont fix status: open -> closed __________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1360> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
