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 Claudiu.Popa, belopolsky, christian.heimes, eric.snow, ethan.furman, ionelmc, jedwards, llllllllll, r.david.murray, rhettinger, steven.daprano, terry.reedy
Date 2015-04-20.13:28:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I in case it wasn't clear, I closed this not because of my "case closed" statement, but because as Eric pointed out we *do* have consistency here: things which check *capabilities* (as opposed to actually *using* the special methods), like callable and Iterable, only look for the existence of the method, consistently.  The fact that you can then get an AttributeError later when actually using the method is unfortunate, but there really isn't anything sensible to be done about it, due to backward compatibility concerns.
Date User Action Args
2015-04-20 13:28:21r.david.murraysetrecipients: + r.david.murray, rhettinger, terry.reedy, belopolsky, christian.heimes, ionelmc, steven.daprano, Claudiu.Popa, ethan.furman, eric.snow, llllllllll, jedwards
2015-04-20 13:28:21r.david.murraysetmessageid: <>
2015-04-20 13:28:21r.david.murraylinkissue23990 messages
2015-04-20 13:28:21r.david.murraycreate