Author scoder
Recipients christian.heimes, inada.naoki, pitrou, rhettinger, scoder, serhiy.storchaka, vstinner
Date 2017-09-14.08:09:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1505376572.87.0.750262039448.issue31336@psf.upfronthosting.co.za>
In-reply-to
Content
One more thing: the fact that the 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. I've created issue 31465 for this.
History
Date User Action Args
2017-09-14 08:09:32scodersetrecipients: + scoder, rhettinger, pitrou, vstinner, christian.heimes, inada.naoki, serhiy.storchaka
2017-09-14 08:09:32scodersetmessageid: <1505376572.87.0.750262039448.issue31336@psf.upfronthosting.co.za>
2017-09-14 08:09:32scoderlinkissue31336 messages
2017-09-14 08:09:32scodercreate