Skip to content
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

Closed
glehmann opened this issue Jul 5, 2018 · 5 comments
Closed

automatic version à la python-versioneer #284

glehmann opened this issue Jul 5, 2018 · 5 comments

Comments

@glehmann
Copy link
Contributor

glehmann commented Jul 5, 2018

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:

> git describe
v0.11.0-136-g2f043654
> mytool --version
0.11.0+136.g2f043654.dirty

and python setup.py sdist generates a package called mytool-0.11.0+136.g2f043654.dirty.tar.gz.

Any chance we can make that happen in poetry?

@mmellison
Copy link

This is whats holding us back from switching to Poetry as well. We love versioneer!

@whoiswes
Copy link

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.

@psafont
Copy link

psafont commented Oct 30, 2018

Related requests: #185 #140

webknjaz added a commit to webknjaz/poetry that referenced this issue Nov 25, 2018
webknjaz added a commit to webknjaz/poetry that referenced this issue Nov 25, 2018
@webknjaz
Copy link

webknjaz commented Dec 1, 2018

Let's close this in favor of #140 + #672 (demo discussion) so that it would be 1 single place with info, not 3 issues asking the same :)

Copy link

github-actions bot commented Mar 3, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants