We've come across a concurrency bug in logging/__init__.py which involves the handling of asynchronous exceptions, such as KeyboardInterrupt, during the execution of logging._acquireLock(). In the ...

Catch the keyboard interrupt signal, so it can be handled by doing nothing instead of throwing an exception in a context where try/catch is not able to deal with it.