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 brett.cannon
Recipients Nathaniel Manista, brett.cannon, docs@python, fdrake, methane, rhettinger
Date 2018-08-30.16:10:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'm not questioning if people have ever created a base exception for an entire package, I'm just asking how often it's actually used when the base exception didn't make sense outside of the rule-of-thumb Nathaniel is pointing out?

For instance, it could makes sense in requests' case to have a base exception to help facilitate catching network-related errors but let through e.g. TypeError. But does that extend to most packages such that users regularly write an 'except' clause catching that package's common base exception type? That's my question and I personally don't have an answer beyond reflecting on this and not really remembering a case where I have (I _can_ remember following this pattern simply because it's habit at this point for some unknown reason :) .
Date User Action Args
2018-08-30 16:10:36brett.cannonsetrecipients: + brett.cannon, fdrake, rhettinger, methane, docs@python, Nathaniel Manista
2018-08-30 16:10:36brett.cannonsetmessageid: <>
2018-08-30 16:10:36brett.cannonlinkissue34538 messages
2018-08-30 16:10:36brett.cannoncreate