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

Switch to versioneer for internal python versions #154

Open
djhoese opened this issue Feb 15, 2019 · 1 comment
Open

Switch to versioneer for internal python versions #154

djhoese opened this issue Feb 15, 2019 · 1 comment
Labels
component:build related to building or release creation

Comments

@djhoese
Copy link
Member

djhoese commented Feb 15, 2019

SatPy and other pytroll packages have switched to using the versioneer tool for identifying the version of a python package. This tool lets you "tag" a release in git which will automatically make the python version python -c 'import polar2grid; print(polar2grid.__version__)' match the name of the last git tag. This goes further where if the installed version isn't tagged (v3.0.0) then it gets the git commit hash added to the end of it (v3.0.0+abcdefg). This is extremely helpful in identifying if one installed version is the same as a released package.

@djhoese djhoese added the component:build related to building or release creation label Feb 15, 2019
@djhoese djhoese added this to the Polar2Grid 2.3 milestone Feb 15, 2019
@djhoese
Copy link
Member Author

djhoese commented Jun 4, 2019

See pytroll/satpy#678 for details but it may be better to use setuptools-scm instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component:build related to building or release creation
Projects
None yet
Development

No branches or pull requests

1 participant