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:33:11
SpamBayes Score 0.0007486251
Marked as misclassified No
Message-id <1290897188.3549.4.camel@localhost.localdomain>
In-reply-to <1290897057.83.0.543895249706.issue10518@psf.upfronthosting.co.za>
Content
> I thought that moratorium meant Guido dis/approval is not applicable to the 3.2

Guido can decide of everything: PEPs, etc. That's what "BDFL" means.
So he can also decide of exceptions to the rules he decided on.
(rules can have exception in any reasonable human society)

> Another listed change was help ease adoption of py3k. How's that helping?

How's it not helping?

I'm not sure what your general point or concern is. Do you have a real
problem with callable() coming back or is it just a formal argument?
History
Date User Action Args
2010-11-27 22:33:12pitrousetrecipients: + pitrou, brett.cannon, georg.brandl, benjamin.peterson, ezio.melotti, eric.araujo, michael.foord, SilentGhost, daniel.urban, lukasz.langa
2010-11-27 22:33:11pitroulinkissue10518 messages
2010-11-27 22:33:11pitroucreate