➜

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 ionelmc
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.08:43:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CANkHFr8VcX-JrtwN1Hq=jgStMYutoAD5EkiVMxBM5ZuPHiwKfw@mail.gmail.com>
In-reply-to <1429502547.13.0.338529314806.issue23990@psf.upfronthosting.co.za>
Content 
On Mon, Apr 20, 2015 at 7:02 AM, Raymond Hettinger <report@bugs.python.org>
wrote:

> 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).

​I think this is largely a product of misunderstanding the issue. As you
can see in the early comments in the thread, the fact that special methods
​use descriptors is really really obscure.

Thanks,
-- Ionel Cristian Mărieș, http://blog.ionelmc.ro
History
Date User Action Args
2015-04-20 08:43:14ionelmcsetrecipients: + ionelmc, rhettinger, terry.reedy, belopolsky, christian.heimes, steven.daprano, r.david.murray, Claudiu.Popa, ethan.furman, eric.snow, llllllllll, jedwards
2015-04-20 08:43:13ionelmclinkissue23990 messages
2015-04-20 08:43:13ionelmccreate