-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
automatic version à la python-versioneer #284
Comments
This is whats holding us back from switching to Poetry as well. We love versioneer! |
I do something similar with setuptools and some homegrown code to programatically determine the version (similar to versioneer). Having the ability to keep such functionality would be ideal. |
Resolves python-poetry#140 Resolves python-poetry#185 Resolves python-poetry#284
Resolves python-poetry#140 Resolves python-poetry#185 Resolves python-poetry#284
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
We are using https://github.com/warner/python-versioneer to version our tools, and it's been working very well so far. Now we are looking into using poetry, but would like to keep a versioneer like behavior that doesn't seem to be possible at this time.
Basically, versioneer automatically generates the package version number based on the current git commits and tags of the package repository. It uses the information from
git describe
to generate the version, and apply a few changes to it to be compatible with python versioning scheme and include some useful info.For example, in our repository, we have:
and
python setup.py sdist
generates a package calledmytool-0.11.0+136.g2f043654.dirty.tar.gz
.Any chance we can make that happen in poetry?
The text was updated successfully, but these errors were encountered: