-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
use versioneer to manage __version__ #981
Conversation
Alternative to the Maybe I am missing something but was there (or is there still) a strong reason against it |
I'll be honest I haven't found |
Oh I see :) The final result would be the same, i.e. E.g. borg project switched from |
It automatically adds all of the SCM-managed files to the sdist. My advice is to create an sdist and diff it with an old one, then add excludes to MANIFEST.IN until they match. |
I'm happy to review a PR that switches us over. The main reason versioneer was introduced in a rush is to unbreak people using a non-release version of Black. |
Sounds good, I can give it a try :) |
__version__
doesn't change.__version__
changes to${TAG}+${COMMITS_SINCE}.g${SHA}${DIRTY}
(TAG
= most recent tag,COMMITS_SINCE
is the number of commits since$TAG
,SHA
is the output ofgit rev-parse HEAD
,DIRTY
is.dirty
if the working copy has uncommited changes), for example:19.3b0+77.gf1a148e.dirty
version
string used for Black's cache to be$SHA
.Fixes #980