A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2008-May/079533.html below:

[Python-Dev] How best to handle the docs for a renamed module?

[Python-Dev] How best to handle the docs for a renamed module? [Python-Dev] How best to handle the docs for a renamed module?Brett Cannon brett at python.org
Sat May 17 07:07:08 CEST 2008
On Fri, May 16, 2008 at 5:49 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> Raymond Hettinger wrote:
>>
>> I say leave the new names in 3.0 and let the 2-to-3 tool do its job.
>> Why confuse the 2.6 landscape with double naming clutter.
>
> To increase the common subset of code which can run on both 2.6 and 3.0
> *without* invoking 2to3?
>

Right. 2.6 is trying to be as much of a reasonable subset of Python
3.0 as possible. This includes module names.

> PEP-8'ifying these names also makes them easier for at least me to remember
> (since I don't have to worry about whether or not the module name includes
> unexpected underscores or strange capitalisation)

That too. =)

-Brett
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4