-
Notifications
You must be signed in to change notification settings - Fork 390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First draft of versioning with versioneer #269
Conversation
2 similar comments
setup.cfg
Outdated
|
||
[versioneer] | ||
VCS = git | ||
style = git-describe |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that this produces a non-PEP440-compliant version string for non-release versions:
$ python setup.py --version
python3.5/site-packages/setuptools/dist.py:407: UserWarning: The version specified ('0.6.0-22-gc172077') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details.
"details." % self.metadata.version
0.6.0-22-gc172077
Personally I prefer pep440-pre
style (0.6.0.post0.dev22
) but the basic pep440
style (0.6.0+22.gc172077
) is closer to git-describe
style; either one makes setuptools happier.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed to pep440.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a big fan of versioneer; go for it!
Installation of
versioneer
into source tree to allow for PyPi versions to be directly derived from git tags based on formatvX.Y.Z
.