Author lemburg
Recipients Nathaniel Manista, ammar2, brett.cannon, docs@python, fdrake, gvanrossum, lemburg, methane, rhettinger
Date 2018-10-01.15:22:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1538407327.6.0.545547206417.issue34538@psf.upfronthosting.co.za>
In-reply-to
Content
Just as extra data point:

It is fairly common to have a common exception class which is then used a mixin class together with the standard exception classes, so that you can indeed identify the source of an exception and catch errors based on the source (e.g. say you want to catch database errors coming from MySQL specifically).

The Python DB-API also requires to create a separate hierarchy for this purpose.

Overall, I wouldn't call this a non-best practice. It depends on the use case, whether it's useful or not.
History
Date User Action Args
2018-10-01 15:22:07lemburgsetrecipients: + lemburg, gvanrossum, fdrake, brett.cannon, rhettinger, methane, docs@python, Nathaniel Manista, ammar2
2018-10-01 15:22:07lemburgsetmessageid: <1538407327.6.0.545547206417.issue34538@psf.upfronthosting.co.za>
2018-10-01 15:22:07lemburglinkissue34538 messages
2018-10-01 15:22:07lemburgcreate