Description of problem:

When the Beaker RPM is installed and pkg_resources is imported before bkr, then "bkr.__version__" will always be reported as the installed version, even if imports of submodules are coming from a source checkout.

How reproducible:

Always

Steps to Reproduce:
1. Install bkr from an RPM
2. Run Beaker with an appropriate PYTHONPATH setting
3. Import pkg_resources
4. Import bkr
5. Check bkr.__version__
  
Actual results:

bkr.__version__ reports the installed version

Expected results:

bkr.__version__ reports the source checkout version

Additional info:

This is actually inherent in the way Python's namespace packages work - the only meaningful package level state allowed is the __path__ attribute that defines where submodules may be found. This is made more obvious in the innate namespace package support in Python 3.3, where the way you indicate a namespace package is not providing an __init__.py file *at all*.

To resolve this issue for Beaker, the current "bkr.__version__" attribute should be moved to "bkr.common.__version__" instead, as retrieving the "bkr.common" sub module will correctly respect PYTHONPATH and report the version that is being used to satisfy submodule imports, rather than the version that was used to create the top level namespace package.

The *only* code in the bkr level __init__.py should be the boilerplate to declare the namespace package.

Until this is changed, in order to build the documentation correctly, it is currently necessary to uninstall any Beaker RPMs.