astropy/astropy — Issue #52: Revision number in package name
Author: astrofrog
Created: 2011-11-07 12:53:41+00:00
State: open

This has been discussed a bit before but I just wanted to open a ticket to discuss this formally. The inclusion of a 'revision number' in the package name is causing site-packages to get cluttered up:

astropy-0.0dev_r153-py2.7-macosx-10.6-x86_64.egg/
astropy-0.0dev_r220-py2.7-macosx-10.6-x86_64.egg/
astropy-0.0dev_r221-py2.7-macosx-10.6-x86_64.egg/
astropy-0.0dev_r227-py2.7-macosx-10.6-x86_64.egg/
astropy-0.0dev_r255-py2.7-macosx-10.6-x86_64.egg/
astropy-0.0dev_r256-py2.7-macosx-10.6-x86_64.egg/
astropy-0.0dev_r277-py2.7-macosx-10.6-x86_64.egg/
astropy-0.0dev_r957-py2.7-macosx-10.6-x86_64.egg/

and I keep having to clear this out manually. I don't think the revision number should be part of the package name, especially since it is not even a real revision number. If one imagines a branch of astropy that is 10 commits ahead of master which is on r100, then if I install that branch I will get r110. However, if a new commit is made on master, and I install that, then the revision number will be r101 which will appear older than my branch. Anyway, all this to say that I think that in the above example there should only be one package installed, which is:

astropy-0.0dev-py2.7-macosx-10.6-x86_64.egg/

In the scenario I described above, this gets overwritten by whatever the latest 0.0 developer version is. I think that the git has could still be stored in astropy, e.g. ``astropy.__githash__``.