[issue28559] Unclear error message when raising wrong type of exceptions

Change by Irit Katriel : -- resolution: -> rejected stage: patch review -> resolved status: pending -> closed ___ Python tracker ___

[issue28559] Unclear error message when raising wrong type of exceptions

Change by Serhiy Storchaka : -- status: open -> pending ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28559] Unclear error message when raising wrong type of exceptions

Changes by Ivan Levkivskyi : -- nosy: +levkivskyi ___ Python tracker ___ ___

[issue28559] Unclear error message when raising wrong type of exceptions

Berker Peksag added the comment: Thanks for the patch, but I find your proposed message less clearer (including NoneType adds unnecessary confusion and people may ask "where did NoneType come from?") Python 2 is different because of historical reasons (pre-BaseException era) so I don't think

[issue28559] Unclear error message when raising wrong type of exceptions

New submission from Dimitri Merejkowsky: Motivation for the patch came from a tweet[1] of David Beazley: def SomeError(Exception): pass raise SomeError('blah') (Note the `def` keyword instead of `class`): If you run that, you get: > TypeError: exceptions must derive from BaseException