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, daniel.urban, eric.araujo, ezio.melotti, georg.brandl, lukasz.langa, michael.foord, pitrou
Date 2010-11-27.22:26:47
SpamBayes Score 3.70846e-05
Marked as misclassified No
Message-id <1290896805.3549.2.camel@localhost.localdomain>
In-reply-to <1290896622.54.0.00173291005258.issue10518@psf.upfronthosting.co.za>
Content
Le samedi 27 novembre 2010 à 22:23 +0000, SilentGhost a écrit :
> SilentGhost <michael.mischurow+bpo@gmail.com> added the comment:
> 
> I thought PEP 3003 was quite unambiguous:

The stated goal of the moratorium is to make it easier for alternate
implementations to catch up with the current language specification.
Bringing back callable() doesn't go against this goal since they already
have implemented it for 2.x.
(not to mention that the implementation should be very simple)

I wouldn't claim this is a authoritative interpretation but, if Guido
doesn't oppose, I would take it for valid :)
History
Date User Action Args
2010-11-27 22:26:49pitrousetrecipients: + pitrou, brett.cannon, georg.brandl, benjamin.peterson, ezio.melotti, eric.araujo, michael.foord, SilentGhost, daniel.urban, lukasz.langa
2010-11-27 22:26:47pitroulinkissue10518 messages
2010-11-27 22:26:47pitroucreate