Author scoder
Recipients scoder
Date 2017-09-14.08:07:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1505376439.65.0.460485878995.issue31465@psf.upfronthosting.co.za>
In-reply-to
Content
Follow-up to issue 31336:
The fact that _PyType_Lookup() does not propagate exceptions leaves some space for ambiguity. If, in a chain of MRO lookups, one would fail and a later one would succeed, is it correct to keep trying? What if the first failure actually failed to see an otherwise existing attribute in that class? We simply can't know because the lookup failed for *some* reason.

I think, the only way to really avoid that ambiguity would be to allow _PyType_Lookup() to raise exceptions, and to make it fail on the first error.
History
Date User Action Args
2017-09-14 08:07:19scodersetrecipients: + scoder
2017-09-14 08:07:19scodersetmessageid: <1505376439.65.0.460485878995.issue31465@psf.upfronthosting.co.za>
2017-09-14 08:07:19scoderlinkissue31465 messages
2017-09-14 08:07:18scodercreate