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 ncoghlan
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-11-03.12:36:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
A point on the safety/correctness front: I remembered we already run arbitrary code at roughly this point in the eval loop, as we have to invoke __iter__ to get the exceptions to check when an iterable is used in except clause.

That means allowing the subclass check hooks to run here isn't as radical a change as I first thought.
Date User Action Args
2013-11-03 12:36:15ncoghlansetrecipients: + ncoghlan, gvanrossum, barry, jamesh, pitrou, benjamin.peterson, eric.araujo, Trundle, cvrebert, daniel.urban, yorik.sar, ethan.furman, Yury.Selivanov, Jim.Jewett, gcbirzan
2013-11-03 12:36:15ncoghlansetmessageid: <>
2013-11-03 12:36:15ncoghlanlinkissue12029 messages
2013-11-03 12:36:15ncoghlancreate