[issue1835] Update version number in __init__.py

Marc-Andre Lemburg added the comment: On 2009-02-05 14:23, Thomas Heller wrote: > Thomas Heller added the comment: > >> The distutils version number is now updated automatically by the Python >> release process, so the comment in that file can be removed. > > How does this mechanism work? I'

[issue1835] Update version number in __init__.py

Thomas Heller added the comment: > The distutils version number is now updated automatically by the Python > release process, so the comment in that file can be removed. How does this mechanism work? I'm wondering if I should use a similar mechanism for the ctypes version number... --

[issue1835] Update version number in __init__.py

Tarek Ziadé added the comment: fixed on r69285 -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue1835] Update version number in __init__.py

Changes by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue1835] Update version number in __init__.py

Tarek Ziadé added the comment: I'll change the comment explaining how things work now. -- assignee: lemburg -> tarek ___ Python tracker ___ __

[issue1835] Update version number in __init__.py

Marc-Andre Lemburg added the comment: The distutils version number is now updated automatically by the Python release process, so the comment in that file can be removed. ___ Python tracker _

[issue1835] Update version number in __init__.py

Akira Kitada added the comment: It seems the version number has been bumped now. Was it okay? -- nosy: +akitada, tarek ___ Python tracker ___

[issue1835] Update version number in __init__.py

Marc-Andre Lemburg added the comment: The version number should only be bumped for major enhancements to distutils or backwards incompatible changes. Have there been any such changes ? __ Tracker <[EMAIL PROTECTED]>

[issue1835] Update version number in __init__.py

Guido van Rossum added the comment: The comment indicates it's not automatic that the version number follows the Python release number. Assigning to MAL who wants to coordinated this according to that same comment. -- assignee: -> lemburg keywords: +easy nosy: +gvanrossum, lemburg prio

[issue1835] Update version number in __init__.py

New submission from Jacques Lemire: In the distutils directory the file __init__.py is not updated to 3.0. -- components: Distutils messages: 59974 nosy: jlp severity: minor status: open title: Update version number in __init__.py type: behavior versions: Python 3.0