I've heard of this thing called "multiple inheritance" :-). Does that fit into your naming scheme?
On Tue, Oct 13, 2020 at 2:03 PM <jmwar...@gmail.com> wrote: > I keep using a syntax of <SomeActualException>.<someSubType> for a reason. > It is piggybacking on an already established exception and in reality just > providing a sub-type that could easily be used by the except block to > determine acceptance. An easy implementation of this still constructs > <SomeActualException> that just has a property of subtype so if you handle > <SomeActualException> explicitly using the current syntax it would catch it > and the parameters you fed in the raise would just be in the e.args. > _______________________________________________ > Python-ideas mailing list -- python-ideas@python.org > To unsubscribe send an email to python-ideas-le...@python.org > https://mail.python.org/mailman3/lists/python-ideas.python.org/ > Message archived at > https://mail.python.org/archives/list/python-ideas@python.org/message/HTBOVAIWVPQP2T7XRMQJSTYMVVSQSQB7/ > Code of Conduct: http://python.org/psf/codeofconduct/ > -- The dead increasingly dominate and strangle both the living and the not-yet born. Vampiric capital and undead corporate persons abuse the lives and control the thoughts of homo faber. Ideas, once born, become abortifacients against new conceptions.
_______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/TEYVTQFSTOTMZ7XHYBORBEM7I77RGJKF/ Code of Conduct: http://python.org/psf/codeofconduct/
