[Python-Dev] Module version variable
Raymond Hettinger
raymond.hettinger at gmail.com
Wed Mar 16 20:00:38 CET 2011
More information about the Python-Dev mailing list
Wed Mar 16 20:00:38 CET 2011
- Previous message: [Python-Dev] Module version variable
- Next message: [Python-Dev] Module version variable
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message: [Python-Dev] Module version variable
- Next message: [Python-Dev] Module version variable
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list