➜

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 eric.snow
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.01:50:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CALFfu7D74kWbLqfJHcvTN7mTmGKRAQ_4SFnj+DkEQPJ_boSr_w@mail.gmail.com>
In-reply-to <CANkHFr8SfSdAuejwZXM=cpqXmXs2DfCWHJfcaUUKxNDzi-mPAA@mail.gmail.com>
Content 
> Ionel Cristian Mărieș added the comment:
> What exactly are you proposing? Getting rid of AttributeError masking?

That isn't really a practical thing to consider, so no. :)  Instead
I'm suggesting there isn't a lot of justification to change the
behavior of callable.  *If* we were to change anything I'd suggest
disallowing AttributeError from a descriptor's getter during special
method lookup.  However, I'm not suggesting that either.  We should
simply leave callable alone (and consistent with the other helpers
that inspect the "special" *capability* of objects).
History
Date User Action Args
2015-04-20 01:50:45eric.snowsetrecipients: + eric.snow, rhettinger, terry.reedy, belopolsky, christian.heimes, ionelmc, steven.daprano, r.david.murray, Claudiu.Popa, ethan.furman, llllllllll, jedwards
2015-04-20 01:50:45eric.snowlinkissue23990 messages
2015-04-20 01:50:45eric.snowcreate