Comment 6 for bug 1379585

Well it was downburst which is a tool I maintain but the problem is that if you have a program that will pull from pypi for dependencies (and you have libvirt-python) listed as a dependency, (like in this case) then it won't be able to detect you already have the python bindings installed from a system package but instead it will try to download the newest libvirt-python from pypi.

This is problematic for multiple reasons. Since you are using a version of libvirt that is maintained by your distribution then its probably better to just use the same version of python bindings of your installed version of libvirt (IE python-libvirt) rather than try to use bleeding edge from pypi (which likely will fail to build anyway against your old version of libvirt).

I am not sure why you wouldn't want the egg info file installed so things like pypi can detect you already have a version installed. Trusty has the egg-info file and this is not an issue on trusty (just precise).