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 r.david.murray
Recipients Trundle, docs@python, eric.snow, georg.brandl, r.david.murray, rhettinger
Date 2011-05-03.21:43:39
SpamBayes Score 6.1593535e-05
Marked as misclassified No
Message-id <1304459021.78.0.854822828688.issue11988@psf.upfronthosting.co.za>
In-reply-to
Content
Well, then I suppose my question is why isn't __contains__ looked up?  Other special methods that don't exist on Y do cause __getattr__ to be called.  Why is __contains__ special?  The docs for __getattr__ don't hint at this possibility either.

I think the people that understand this must have a mental model of how the interpreter looks up methods that has some pieces that are missing from mine.  I guess I'd like those bits to be made explicit in the special method lookup docs, or if they are already documented somewhere, for there to be a pointer to them in the special method lookup docs.
History
Date User Action Args
2011-05-03 21:43:41r.david.murraysetrecipients: + r.david.murray, georg.brandl, rhettinger, Trundle, docs@python, eric.snow
2011-05-03 21:43:41r.david.murraysetmessageid: <1304459021.78.0.854822828688.issue11988@psf.upfronthosting.co.za>
2011-05-03 21:43:39r.david.murraylinkissue11988 messages
2011-05-03 21:43:39r.david.murraycreate