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 yorik.sar
Recipients Jim.Jewett, Trundle, Yury.Selivanov, barry, benjamin.peterson, cvrebert, daniel.urban, eric.araujo, ethan.furman, gcbirzan, gvanrossum, jamesh, ncoghlan, pitrou, yorik.sar
Date 2013-10-21.19:34:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Can someone please point out why do we have to do that dance with recursion limit?

I've came upon this problem as well. I had some (bad) API I had to work with. It always raised the same exception with the only difference in the message. So I thought I could do something like this:

def message_contains(msg):
    class _MyExc(object):
        def __instancecheck__(self, exc):
            return msg in exc.args[0]
    return _MyExc

But after I tried it in number of different ways I found out that it's not possible.

So here's another reason to change this behavior.
Date User Action Args
2013-10-21 19:34:25yorik.sarsetrecipients: + yorik.sar, gvanrossum, barry, jamesh, ncoghlan, pitrou, benjamin.peterson, eric.araujo, Trundle, cvrebert, daniel.urban, ethan.furman, Yury.Selivanov, Jim.Jewett, gcbirzan
2013-10-21 19:34:25yorik.sarsetmessageid: <>
2013-10-21 19:34:25yorik.sarlinkissue12029 messages
2013-10-21 19:34:24yorik.sarcreate