This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients benjamin.peterson, brett.cannon, ncoghlan
Date 2011-06-07.04:12:13
SpamBayes Score 6.568827e-09
Marked as misclassified No
Message-id <1307419934.4.0.45216742345.issue12273@psf.upfronthosting.co.za>
In-reply-to
Content
Benjamin's AST modification checkins switched directly from the SVN revision number (as a string) to the hg revision hash.

While that preserves uniqueness, it makes ordering difficult to determine.

The last AST version in 3.2 was '82163' (and it was '82160' in 2.7).

I would like to change the version number calculation to something like:

  '9.x.y.zzzzzzz'

where

  9 is a prefix to get 3.3+ ast.__version__ values to sort higher than earlier versions
  x.y is the Python version so later versions sort higher than earlier versions in the future
  zzzzzz is the hg version id, so versions during development of a release remain unique, even if they can't be readily ordered.

This would require changes to ast.py (to add the 9.x.y prefix) and to release.py (to check that the 'x.y' prefix is correct in the current release)
History
Date User Action Args
2011-06-07 04:12:14ncoghlansetrecipients: + ncoghlan, brett.cannon, benjamin.peterson
2011-06-07 04:12:14ncoghlansetmessageid: <1307419934.4.0.45216742345.issue12273@psf.upfronthosting.co.za>
2011-06-07 04:12:13ncoghlanlinkissue12273 messages
2011-06-07 04:12:13ncoghlancreate