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 rhettinger
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.04:02:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1429502547.13.0.338529314806.issue23990@psf.upfronthosting.co.za>
In-reply-to
Content
Unless there are some serious objections, I propose to close this on the basis of "practicality beats purity" (and as David Murray noted, there may not be a pure answer).   Eric Snow's comments are dead-on.

AFAICT, there isn't a real problem here and the API for better-or-worse has proven to be usable in practice (the callable() API has been around practically forever and the descriptor protocol has been around since Py2.2 -- if there were a real issue here, it would have reared it head long ago).
History
Date User Action Args
2015-04-20 04:02:27rhettingersetrecipients: + rhettinger, terry.reedy, belopolsky, christian.heimes, ionelmc, steven.daprano, r.david.murray, Claudiu.Popa, ethan.furman, eric.snow, llllllllll, jedwards
2015-04-20 04:02:27rhettingersetmessageid: <1429502547.13.0.338529314806.issue23990@psf.upfronthosting.co.za>
2015-04-20 04:02:27rhettingerlinkissue23990 messages
2015-04-20 04:02:26rhettingercreate