aboutsummaryrefslogtreecommitdiffstats
path: root/libbe/version.py
Commit message (Collapse)AuthorAgeFilesLines
* version: convert to Python 3 compatibilityW. Trevor King2012-11-121-10/+12
|
* doc: clean up top level module docstringsW. Trevor King2012-10-261-6/+7
|
* version: use abbreviated SHA instead of explicit _VERSION in master branchW. Trevor King2012-10-251-2/+2
| | | | | | Only official releases get a version number, which should help avoid confusion. If you're running a live checkout, you shouldn't be scared off by SHAs.
* Ran update-copyright.py.W. Trevor King2012-10-161-1/+1
|
* Ran update-copyright.py.W. Trevor King2012-02-161-10/+10
|
* Run update_copyright.py.W. Trevor King2011-05-251-1/+2
|
* Bumped to version 1.0.01.0.0Chris Ball2011-01-081-2/+2
|
* Default to "unknown" version info if libbe._version is missing.W. Trevor King2010-09-051-3/+12
|
* Ran update_copyright.pyW. Trevor King2010-06-221-12/+14
|
* Updated _version.py and version.py to work with GitW. Trevor King2010-06-221-5/+5
|
* Updated copyright informationW. Trevor King2010-01-011-1/+1
|
* Added storage.Storage.storage_version() and command.InvalidStorageVersion.W. Trevor King2009-12-271-2/+2
| | | | Now commands automatically check for storage version compatibility.
* Fixed libbe.storage.util.upgradeW. Trevor King2009-12-271-2/+8
| | | | | | | | | | | | | Note that it only upgrades on-disk versions, so you can't use a non-VCS storage backend whose version isn't your command's current storage version. See #bea/110/bd1# for reasoning. To see the on-disk storage version, look at .be/version To see your command's supported storage version, look at be --full-version I added test_upgrade.sh to exercise the upgrade mechanism on BE's own repository.
* Added libbe.version, wrapping the auto-generated libbe._version.W. Trevor King2009-09-151-0/+50
Two major benefits: 1) Programatic access to the BE version. Previously the version-string logic was internal to the commandline interface ./be, which left the other interfaces hanging. 2) Simple to override auto-generated revision id version with any string you like (by setting libbe.version._VERSION, if that's the way you want to run things or the way your packaging system requires. Note that other modules should never read libbe.version._VERSION, since it may not be defined. Instead they should use the output of libbe.version.version().