[Python-Dev] Adding PEP consistent aliases for names that don't currently conform

Steve Holden steve at holdenweb.com
Fri Mar 27 08:07:33 CET 2009


Guido van Rossum wrote:
> On Thu, Mar 26, 2009 at 10:26 PM, Greg Ewing
> <greg.ewing at canterbury.ac.nz> wrote:
>> Guido van Rossum wrote:
>>
>>> I'll gladly take that as an added rationalization of my plea not to
>>> change datetime.
>> In the case of datetime, could perhaps just the
>> module name be changed so that it's not the same
>> as a name inside the module? Maybe call it
>> date_time or date_and_time.
> 
> I don't think that's advisable ATM -- again, something we should have
> done for 3.0, but now it's too late.
> 
> I really don't want to set a trend where 3.1 is backwards incompatible
> with 3.0 *except* in cases where we were really planning to kill
> something in 3.0 and accidentally forgot to quite remove it completely
> (like cmp()).
> 
Right. Otherwise pprint.pprint becomes pprint.p_print and ...

That way madness lies. Besides which, what a terrific opportunity to
castigate the Py3k developers forever. Opportunities like that don't
come by every day ;-)

regards
 Steve
-- 
Steve Holden           +1 571 484 6266   +1 800 494 3119
Holden Web LLC                 http://www.holdenweb.com/
Want to know? Come to PyCon - soon! http://us.pycon.org/



More information about the Python-Dev mailing list