Message312874
With issue 17611 merged (which moves stack unwinding to the compiler), I expect the exact details of this problem to have changed, but the general problem still exists: Ctrl-C may lead to __exit__ (or __aexit__) not being called even after __enter__ (or __aenter__) returns successfully, and this may happen even for context managers implemented with uninterruptible methods (e.g. in C in CPython without calling back into any Python code). |
|
Date |
User |
Action |
Args |
2018-02-26 02:41:47 | ncoghlan | set | recipients:
+ ncoghlan, gregory.p.smith, njs, Mark.Shannon, erik.bray, jdemeyer, yselivanov, deleted0524, xgdomingo |
2018-02-26 02:41:46 | ncoghlan | set | messageid: <1519612906.89.0.467229070634.issue29988@psf.upfronthosting.co.za> |
2018-02-26 02:41:46 | ncoghlan | link | issue29988 messages |
2018-02-26 02:41:46 | ncoghlan | create | |
|