How to handle version skew between baz and pybaz
================================================

Check the value of pybaz.backend.version.

This is an instance of the pybaz.compat.BazaarCommandVersion class, which has
all the docstrings you can expect (epydoc is your friend).

In particular it provides pybaz.backend.version.string you should use for
reporting the baz version to the user.

Also check the value of pybaz.backend.compatibility.

It can take several value depending on what pybaz declares to support and the
version of baz used.

    * baz is a supported release

      pybaz.compat.status.OK

    * baz is a future release, pybaz must be upgraded

      pybaz.compat.status.BAZ_TOO_NEW

    * baz is an unsupported obsolete release, baz should be upgraded

      pybaz.compat.status.UNSUPPORTED

    * baz and pybaz are prereleases for the same version, if a problem arises,
      both must be upgraded to the latest release before reporting an issue.

      pybaz.compat.status.COTM

Since I am (according to my co-workers) an anal retentive API fascist, I have
defined a little enum type to force you to you to use the proper objects
instead of a hard-coded literals.