[MERGE] Fix two bugs in api versioning support - 279447 and 279451
John Arbash Meinel
john at arbash-meinel.com
Tue Oct 7 15:39:42 BST 2008
-----BEGIN PGP SIGNED MESSAGE-----
Robert Collins wrote:
> This tries to make the api support in bzr more suitable for bzr-svn.
I'm a bit curious how the requested range works with how we increment
the ranges. Regardless, I think if it gets bzr-svn to use it, good enough.
I like the change to plugin loading messages. I don't know if bzr-svn
could to it more as-needed rather than on every command. bzrtools did
manage to do that most of the time.
=== modified file 'bzrlib/api.py'
- --- bzrlib/api.py 2007-06-26 08:52:20 +0000
+++ bzrlib/api.py 2008-10-07 04:51:25 +0000
@@ -80,3 +80,24 @@
minimum = get_minimum_api_version(object_with_api)
if wanted_api < minimum or wanted_api > current:
raise IncompatibleAPI(object_with_api, wanted_api, minimum,
+def require_any_api(object_with_api, wanted_api_list):
^- two spaces here:
+ :param wanted_api: A list of API versions, any of which being
+ :return None:
+ :raises IncompatibleAPI: When the wanted_api is not supported by
^- as bialix pointed out, ":return: None"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the bazaar