Hello,
When using the standard "requirements.txt" files for installation
package dependencies, I noticed that "libvirt-python" would attempt to
be installed by "pip" even when the equivalent RPM package is already
installed.
For instance, on a Fedora 25 system:
$ rpm -q libvirt-python
libvirt-python-2.2.0-1.fc25.x86_64
$ python -e 'import pkg_resources;
pkg_resources.get_distribution("libvirt-python")'
...
pkg_resources.DistributionNotFound: The 'libvirt-python' distribution
was not found and is required by the application
The provider (the actual module) is actually present, but (rightfully
so) under the name "libvirt":
$ python -c 'import pkg_resources; print
pkg_resources.get_provider("libvirt")'
<pkg_resources.DefaultProvider instance at 0x7fdfbc67a488>
At first sight, this seems to be caused by the lack of an "egg-info"
file, such as:
$PYTHON_SITE_PACKAGES/libvirt_python-2.2.0-py2.7.egg-info
I'm reporting a supposedly packaging issue here since the libvirt-python
setup.py file itself includes support for a custom rpm command.
Please advise if any of this is intentional, and/or whether this should
indeed be reported here or on downstream only.
Regards,
--
Cleber Rosa
[ Sr Software Engineer - Virtualization Team - Red Hat ]
[ Avocado Test Framework - avocado-framework.github.io ]
[ 7ABB 96EB 8B46 B94D 5E0F E9BB 657E 8D33 A5F2 09F3 ]
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
