Skip to content
This repository has been archived by the owner on Nov 23, 2023. It is now read-only.

Maintain version numbers consistently #29

Open
gnn opened this issue Mar 20, 2017 · 1 comment
Open

Maintain version numbers consistently #29

gnn opened this issue Mar 20, 2017 · 1 comment
Assignees
@gnn
Labels
enhancement
Milestone
v0.0.7

Comments

@gnn
Copy link
Member

gnn commented Mar 20, 2017

I added oemof.db.__version__ in the 0.0.5 release so that the version number can be queried at runtime. That means we now have two sources of version numbers, the setup.py file and oemof.db.__version__. Due to how oemof/db/__init__.py is written, the latter can not be used in the former. For that reason I should figure out how to use bumpversion to maintain those version numbers consistently or find a different solution to have a single source for this again.
@gnn gnn changed the title Use bumpversion to maintain version numbers Use [bumpversion](https://github.com/peritus/bumpversion) to maintain version numbers Mar 20, 2017
@gnn gnn changed the title Use [bumpversion](https://github.com/peritus/bumpversion) to maintain version numbers Maintain version numbers consistently Mar 20, 2017
gnn added a commit that referenced this issue Mar 20, 2017
@gnn
Add __version__ to oemof.db
eff19dd 
That means we now have two sources of the version number in our code.
The `setup.py` file and the `__version__` in `oemof/db/__init__.py`.
For now that's not a problem, but we should eventually move to using
[`bumpversion`][0] to maintain those version numbers.
See issue #29 for updates on this.

[0]: https://github.com/peritus/bumpversion
@uvchik uvchik added this to the v0.0.7 milestone May 25, 2020
@uvchik
Copy link
Member

uvchik commented May 25, 2020

Does it work now?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@gnn gnn

Labels
enhancement
Projects
None yet
Milestone
v0.0.7
Development

No branches or pull requests
2 participants
@gnn @uvchik