mirror of
https://gitlab.com/libvirt/libvirt-python.git
synced 2024-10-26 07:55:06 +03:00
Python language binding for libvirt native C API
4733e2a2d1
This refresh switches the CI for contributors to be triggered by merge requests. Pushing to a branch in a fork will no longer run CI pipelines, in order to avoid consuming CI minutes. To regain the original behaviour contributors can opt-in to a pipeline on push git push <remote> -o ci.variable=RUN_PIPELINE=1 This variable can also be set globally on the repository, though this is not recommended. Upstream repo pushes to branches will run CI. The use of containers has changed in this update, with only the upstream repo creating containers, in order to avoid consuming contributors' limited storage quotas. A fork with existing container images may delete them. Containers will be rebuilt upstream when pushing commits with CI changes to the default branch. Any other scenario with CI changes will simply install build pre-requisite packages in a throaway environment, using the ci/buildenv/ scripts. These scripts may also be used on a contributor's local machines. With pipelines triggered by merge requests, it is also now possible to workaround the inability of contributors to run pipelines if they have run out of CI quota. A project member can trigger a pipeline from the merge request, which will run in context of upstream, however, note this should only be done after reviewing the code for any malicious CI changes. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> |
||
|---|---|---|
| .github/workflows | ||
| ci | ||
| examples | ||
| tests | ||
| .ctags | ||
| .dir-locals.el | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| AUTHORS.in | ||
| CONTRIBUTING.rst | ||
| COPYING | ||
| COPYING.LESSER | ||
| generator.py | ||
| HACKING | ||
| libvirt-lxc-override-api.xml | ||
| libvirt-lxc-override.c | ||
| libvirt-override-api.xml | ||
| libvirt-override-virConnect.py | ||
| libvirt-override-virDomain.py | ||
| libvirt-override-virDomainCheckpoint.py | ||
| libvirt-override-virDomainSnapshot.py | ||
| libvirt-override-virNetwork.py | ||
| libvirt-override-virStoragePool.py | ||
| libvirt-override-virStream.py | ||
| libvirt-override.c | ||
| libvirt-override.py | ||
| libvirt-python.spec.in | ||
| libvirt-qemu-override-api.xml | ||
| libvirt-qemu-override.c | ||
| libvirt-qemu-override.py | ||
| libvirt-utils.c | ||
| libvirt-utils.h | ||
| libvirtaio.py | ||
| Makefile | ||
| MANIFEST.in | ||
| README | ||
| requirements-test.txt | ||
| setup.py | ||
| tox.ini | ||
| typewrappers.c | ||
| typewrappers.h | ||
Libvirt Python Binding README ============================= This package provides a python binding to the libvirt.so, libvirt-qemu.so and libvirt-lxc.so library APIs. It is written to build against any version of libvirt that is 0.9.11 or newer. This code is distributed under the terms of the LGPL version 2 or later. Requirements ------------ To build the libvirt python binary requires the GCC and pkg-config tools, and development headers for the libvirt and python libraries. Building and installing ----------------------- The module can be built by following the normal python module build process python setup.py build sudo python setup.py install or to install as non-root python setup.py build python setup.py install --user If python-pytest is installed, you can test the package with python setup.py test A makefile shim is provided so that you can do make && make check rather than directly invoking setup.py. As of libvirt 1.2.6, it is possible to develop against an uninstalled libvirt.git checkout, by setting PKG_CONFIG_PATH and LD_LIBRARY_PATH environment variables to point into that libvirt tree; you can even automate this by using libvirt's run script: /path/to/libvirt/run python setup.py build Patches for this code should be submitted as merge requests to the project page on gitlab. See CONTRIBUTING.rst for more information.