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 steve.dower
Recipients benjamin.peterson, brett.cannon, larry, matrixise, ned.deily, steve.dower
Date 2017-03-04.20:42:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1488660154.99.0.562536332169.issue27593@psf.upfronthosting.co.za>
In-reply-to
Content
I just did my build for 3.6.1rc1 and it looks like `git name-rev --name-only --tags HEAD` returns "3.6.1rc1^0" for some reason.

Perhaps "git describe" is the better command to use here? From what I've seen of that, it should do "tag if tagged, else short hash" by default, and we can do "git describe --dirty=<suffix>" to get an extra marker for when it has been modified. (Though this may mean taking GITTAG back out of our scripts.)

Otherwise, I think the releases are no longer blocked on this, and we can take a bit of time to figure out the right format.
History
Date User Action Args
2017-03-04 20:42:35steve.dowersetrecipients: + steve.dower, brett.cannon, larry, benjamin.peterson, ned.deily, matrixise
2017-03-04 20:42:34steve.dowersetmessageid: <1488660154.99.0.562536332169.issue27593@psf.upfronthosting.co.za>
2017-03-04 20:42:34steve.dowerlinkissue27593 messages
2017-03-04 20:42:34steve.dowercreate