Steve Dower added the comment: 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. ---------- priority: release blocker -> high _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27593> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
