-
Notifications
You must be signed in to change notification settings - Fork 353
Request: Tagged Releases #91
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
Comments
Hi @qwj is there a plan to implement this? FWIW, with the help of tools like |
I am wanting to package this for openSUSE, and I also need tagged releases, and even better would be for the PyPI sdist to contain the test modules. |
@yan12125 setuptools_scm was added. Thanks for the commit and advices. |
Thanks, the latest PyPI sdist works fine! |
Upstream improved the sdist [1] [1] qwj/python-proxy#91 git-svn-id: file:///srv/repos/svn-community/svn@770906 9fca08f4-af9d-4005-b8df-a31f2cc04f65
Upstream improved the sdist [1] [1] qwj/python-proxy#91 git-svn-id: file:///srv/repos/svn-community/svn@770906 9fca08f4-af9d-4005-b8df-a31f2cc04f65
Looking at the pypi repo for this project, the version numbers are clear. However, it's not clear when looking at this Git repo which commit corresponds to which version release. Would you be able to tag the commits corresponding to the pypi releases going forward? Something akin to how numpy does it: https://github.com/numpy/numpy/tags
The main reason I am asking is that I repackage this library for use in some software distributions, and I prefer to run your tests whenever possible. However, those tests are only included in the GitHub source, and not the tar.gz sdist on pypi, necessitating fetching from the GitHub repo.
https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/managing-releases-in-a-repository
The text was updated successfully, but these errors were encountered: