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 pitrou
Recipients SilentGhost, benjamin.peterson, brett.cannon, eric.araujo, ezio.melotti, georg.brandl, lukasz.langa, pitrou
Date 2010-11-25.14:55:14
SpamBayes Score 0.0402806
Marked as misclassified No
Message-id <1290696910.3556.1.camel@localhost.localdomain>
In-reply-to <1290678973.51.0.496980119878.issue10518@psf.upfronthosting.co.za>
Content
> I'm with Ezio here. I'm -1 for callable(), +0 for iscallable() (there
> should be preferably one obvious way to do it and using isinstance()
> seems to be that way at this point).

The thing is, "isisinstance(x, collections.Callable)" is hardly obvious
to anybody, while callable() is.
As for the naming, it's the same as in 2.x, which is a good enough
reason for me. Nobody stops you from calling your callables "callable"
anyway, or your maxima "max" and your sums "sum".
History
Date User Action Args
2010-11-25 14:55:17pitrousetrecipients: + pitrou, brett.cannon, georg.brandl, benjamin.peterson, ezio.melotti, eric.araujo, SilentGhost, lukasz.langa
2010-11-25 14:55:14pitroulinkissue10518 messages
2010-11-25 14:55:14pitroucreate