added versioneer for versioning #150
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Versioneer is nice because you never have to (or forget to) update the
__version__
string. To make a new release version, you just add a git tag. When changes are made after a tag, the git commit is indicated in the version, so it might be something like0.3.0+17.g39a420e
indicating the code is based on git commit39a420e
which is 17 commits after the0.3.0
tag.The versioneer code is kept in _version.py so that version.py can be left alone for backwards compatibility. This seems kind of redundant, but might help a few people.