CTRL-C keeps being a problem
Strongest feedback I heard during the IT-BLresp day.
I propose the following:
- Remove all kill masks
- Remove all bare excepts (and reinstate
E722
for flake8) - Whenever you capture
BaseException
or a derived one likeKeyboardInterrupt
, run the cleanup in a different greenlet with a very small timeout. This also goes for anyGreenletExit
captures andfinally
blocks. Perhaps some others as well.
With these things in our code base, it should be no surprise that CTRL-C is not reliable.
Edited by Wout De Nolf