Merge #138: Rebuilds cache on version change and de-duplicate version definition.
See #86 and #129. The version number is now only stored in pubs/version.py. setup.py loads the version from the file as well as does pubs/__init__.py. The cache structure changes to now include the version of the code which wrote the cache, which enables rebuilding the cache on version change. Loading an old cache (i.e. without the version) fails and triggers a rebuild (so does loading the new cache from the old code) so moving across this change is transparent here. The code also switches to version 0.8.dev1 to trigger a cache rebuild (and also because the milestone is almost there). In general we will need to bump the version number to a development one each time a change makes loading old cache incompatible. There is no test for that at the moment so this means testing new code on a local bibliography repository before pushing to master. #129 discussed using git versions, which is not so easy to integrate nicely with setuptools. This is why I chose to stick with manually changing version numbers when necessary (which should not be so often).main
commit
47b69820b8
@ -1 +1 @@
|
||||
__version__ = '0.7.0'
|
||||
from .version import __version__
|
||||
|
@ -0,0 +1 @@
|
||||
__version__ = '0.8.dev1'
|
Loading…
Reference in new issue