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

use versioneer for standard versioning #29

Closed
gidden opened this issue Jun 5, 2018 · 1 comment
Closed

use versioneer for standard versioning #29

gidden opened this issue Jun 5, 2018 · 1 comment
Labels
enh New features & functionality

Comments

@gidden
Copy link
Member

gidden commented Jun 5, 2018

Previously, we tried to import the package to get the version number in setup.py. This broke our conda build. It appears that versioneer can fix this. See, e.g., xarray.

@gidden gidden added the enh New features & functionality label Jun 5, 2018
@gidden
Copy link
Member Author

gidden commented Nov 21, 2018

this is not possible given that we do versioning in the GAMS code. we may want to think about revisiting this strategy as there is now non-trivial amount of code (e.g., message_ix.Scenario class). @danielhuppmann let me know what you think. Closing this for now, but we may want to have two versions here, the code and the model.

@gidden gidden closed this as completed Nov 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enh New features & functionality
Projects
None yet
Development

No branches or pull requests

1 participant