➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mbussonn
Recipients ezio.melotti, gregory.p.smith, mbussonn, mrabarnett, serhiy.storchaka
Date 2019-12-09.18:33:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1575916390.23.0.231078286947.issue38981@roundup.psfhosted.org>
In-reply-to
Content 
> RECompileError, REParseError, RESyntaxError, REError, CompileError, ParseError, SyntaxError or Error, 

> Many modules [...] have an exception named just Error

RECompileError, REParseError, RESyntaxError, REError, CompileError, ParseError are all fine with me. 

SyntaxError would be super confusing IMHO.
Remember the StackTrace does not get the fully qualified name, so it would be hard to distinguish from a SyntaxError with the Python Syntax.

aifc, binhex, sunau, uu, xdrlib might be removed with PEP 594, And I find  `Error` not informative enough. It suffers from the same issues as above, as stack traces do not have the full qualified name. 

I would also add that being able to search and find all occurrences of a given exceptions is useful, and that Error is too generic.

Let me know your choice and I can rename.
History
Date User Action Args
2019-12-09 18:33:10mbussonnsetrecipients: + mbussonn, gregory.p.smith, ezio.melotti, mrabarnett, serhiy.storchaka
2019-12-09 18:33:10mbussonnsetmessageid: <1575916390.23.0.231078286947.issue38981@roundup.psfhosted.org>
2019-12-09 18:33:10mbussonnlinkissue38981 messages
2019-12-09 18:33:09mbussonncreate