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, ethan.furman, ionelmc, jedwards, llllllllll, terry.reedy
Date 2015-04-18.17:43:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CANkHFr8jCOFkDGAT5gX2mq0OYD1pAUOk5KFhJaEbchRhwaxU_A@mail.gmail.com>
In-reply-to <1429378510.24.0.470406323809.issue23990@psf.upfronthosting.co.za>
Content
On Sat, Apr 18, 2015 at 8:35 PM, Christian Heimes <report@bugs.python.org>
wrote:

> You also haven't shown that this behavior violates the documentation and
> language spec.

​How can I show it violates the "spec" when there's not such thing? :-)
AFAIK, `callable` is not specified in any PEP. Please give some references
when you make such statements.

​[...] write a PEP and convince all implementors of Python implementations
> to change the current way callable() and other protocols like iter work.

`iter` works fine, as outlined above? Am I missing something? What other
protocols do you have in mind, wrt honoring descriptors?

Thanks,
-- Ionel Cristian Mărieș, http://blog.ionelmc.ro
History
Date User Action Args
2015-04-18 17:43:12ionelmcsetrecipients: + ionelmc, terry.reedy, belopolsky, christian.heimes, Claudiu.Popa, ethan.furman, llllllllll, jedwards
2015-04-18 17:43:12ionelmclinkissue23990 messages
2015-04-18 17:43:12ionelmccreate