On Tue, 2 Mar 2021 at 21:46, Irit Katriel via Python-Dev <python-dev@python.org> wrote: > As an aside - I found it interesting that the option to wrap BaseException > instances by an Exception, which came up a couple of times in this thread, > didn't generate any anxiety.
Probably because it wasn't clear that was ever being proposed... (or at least the implication wasn't obvious - presumably this is somehow related to BaseExceptions being accumulated in ExceptionGroups?) :-( I would consider it essential that if someone hits Ctrl-C and that generates a KeyboardInterrupt, then: 1. That KeyboardInterrupt will *not* get caught by exception handlers only interested in Exception instances 2. That KeyboardInterrupt *will* get caught by any handler that does an explicit `except KeyboardInterrupt` or an `except BaseException`. To me, that's pretty much essential to correct Ctrl-C handling in any app (never ignore a user's Ctrl-C and always exit cleanly if one is raised). That might mean that BaseException instances shouldn't be "groupable", but I don't want to comment on that until I've properly read the PEP (I've skimmed it now, but only superficially). At a minimum, I'd consider it a bug for library code to manually wrap a KeyboardInterrupt in an exception group (just like code that catches KeyboardInterrupt and re-raises it as a ValueError would be today). Paul _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/S5SPIFHGWASEGKBITWPDDRXOU33NLG46/ Code of Conduct: http://python.org/psf/codeofconduct/
