Repository navigation
Improve version.py generation #8
Description
I've been working on my own version.py generation for STScI's packages--it works pretty similarly, but with a couple differences:
- I also started out making it an extension of the build_py command, but I ended up changing it to regenerate the file on every setup.py run--this ensures that an updated version.py file is created for commands such as 'develop' and 'sdist'. It doesn't seem to add any noticeable time to running setup.py.
- The version.py uses the SVN revision info getter to automatically update its SVN info on import if the package is installed in develop mode. That way, when installed in develop mode the revision is always up to date. I would want the same for git. It doesn't do this if the package is not installed in develop mode, so it doesn't hurt import time otherwise. The code for doing that is just part of the version.py template.
I'm open to other ideas for exactly how to implement this, but I would want to add these capabilities.
Activity
embray commentedon Oct 12, 2011
I should add--in my version of this I just put the version.py directly into the source (rather than in the build/ dir as a build_py extension would do). Then I just use svn:ignore (or in this case .gitignore) on it.
embray commentedon Oct 13, 2011
Issue #12 illustrates what I'm talking about here (has GitHub added the ability to attach a pull request to an existing issue yet?)
Merge pull request #8 from astrofrog/quantity/allow-arrays-fix
Merge pull request #8 from eteq/mdboom-travis-build-status-badge
Merge pull request #12 from iguananaut/fix-setup-version
Merge pull request #8 from astrofrog/quantity/allow-arrays-fix
Merge pull request astropy#8 from nden/fix-model-meta
@adrn review comment #8
Merge pull request astropy#8 from jehturner/linear-fitter-weights
adjusted doc dropdown per @mdboom's suggestion