[Tutor] managing version numbers (with versioneer?)

[Albert-Jan Roskam]

Hi,
 
I was wondering what is the best way to manage version strings during the release process. I was browsing on the web and I found out about the 'versioneer' package, which seems very promising: "[During the creation of a bdist/sdist] they invoke “git describe” (with –tags –always –dirty) to come up with a fine-grained version string. If you’re sitting on a tag, you get just “1.4″. If you’re after a tag, you’ll get something like “1.4-8-gf7283c2″, which means there are 8 commits after the 1.4 tag, and the abbreviated SHA1 revision ID is f7283c2. And if your tree has uncommitted changes, you’ll get “1.4-8-gf7283c2-dirty”. " [http://blog.mozilla.org/warner/2012/01/31/version-string-management-in-python-introducing-python-versioneer/]

What are the best practices here? Is there some, possibly better, alternative to versioneer? I am using git on linux ubuntu 12, and setuptools with Python 2.7.3.

Regards,
Albert-Jan


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
All right, but apart from the sanitation, the medicine, education, wine, public order, irrigation, roads, a 
fresh water system, and public health, what have the Romans ever done for us?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~