On 16 May 2015 at 00:28, Daniel P. Berrange <berra...@redhat.com> wrote:
> is not actually working around a bug the libvirt hypervisor. It is in fact
> a bug in the libvirt-python API binding. As such we don't actually need to
> increase the min required libvirt to be able to remove that check. In fact
> increasing the min required libvirt is the wrong thing todo, because it is
> possible for someone to have the min required libvirt, but by accessing it
> via an older libvirt-python which still has the bug.
>
> So what's really needed is a dep on libvirt-python >= 1.2.0, not libvirt.
>
> We don't express min required versions for libvirt-python in the
> requirements.txt file though, since it is an optional package and we
> don't have any mechanism for recording min versions for those AFAIK.
The next release of pbr (due Mondayish) has support for optional
dependencies ('extras' in setuptools parlance) - which will allow
this. We're having a session about such things in Vancouver too.
-Rob
--
Robert Collins <rbtcoll...@hp.com>
Distinguished Technologist
HP Converged Cloud
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
