RetroSearch Browse

Wed Mar 16 20:00:38 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-March/109390.html

On Mar 16, 2011, at 11:33 AM, R. David Murray wrote:

> On Wed, 16 Mar 2011 13:33:20 -0400, Michael Foord <fuzzyman at voidspace.org.uk> wrote:
>> On 16/03/2011 12:39, Alexander Belopolsky wrote:
>>> I was editing the turtle module (for issue11571, if you are
>>> interested) when I noticed that it has the following line:
>>> 
>>> _ver = "turtle 1.1b- - for Python 3.1   -  4. 5. 2009"
>>> 
>> 
>> unittest also has an outdated (and unmaintained) version number that I 
>> would like to remove. Standard library modules should be versioned by 
>> the release of Python they are packaged with (unless they are externally 
>> maintained I guess) and so should preferably *not* carry version info.
> 
> The email package has an internal version (which changes no more often
> than CPython's, but may change slower).  Existing code in the field
> tests this version attribute, so I don't think it should be deleted.

The version number in the decimal module refers to the version of the
spec that is being complied with.  I would like that version number
to remain in the module.

There are probably other cases where the version number is useful.

Raymond

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

Showing content from https://mail.python.org/pipermail/python-dev/2011-March/109390.html below:

[Python-Dev] Module version variable