mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-24 22:55:23 +00:00
4165d68aaa
The API definition accepts "flags" argument, however, the implementation ignores it, though "flags" is unused currently, we should expose it instead of hard coding, the API implementation inside hypervisor driver is responsible to check if the passed "flags" is valid. |
||
---|---|---|
.. | ||
tests | ||
generator.py | ||
libvirt-override-api.xml | ||
libvirt-override-virConnect.py | ||
libvirt-override-virStream.py | ||
libvirt-override.c | ||
libvirt-override.py | ||
libvirt-qemu-override-api.xml | ||
libvirt-qemu-override.c | ||
Makefile.am | ||
README | ||
TODO | ||
typewrappers.c | ||
typewrappers.h |
libvirt Python Bindings README ============================== Most of the libvirt python binding code is automatically generated using the script generator.py, and the API description from docs/libvirt-api.xml Manually written files: - libvirt-override.c: methods where the C binding needs to be hand crafted - libvirt-override.py: global methods where the C and python bindings have different args - libvirt-override-api.xml: methods where the auto-extracted API docs are not suitable for python auto-generator. Overriding this if the method is going into libvirt-override.c, but we still want auto-generated libvirt-override.py - libvirt-override-virConnect.py: virConnect class methods - typewrappers.h,.c: Python object wrappers for each libvirt C object Auto-generated files: - libvirt.py: The main python binding. Comprises auto-generated code, along with contents from libvirt-override.py and libvirt-override-virConnect.py - libvirt.c, libvirt.h: The C glue layer for the python binding. Comprises auto-generated code, along with libvirt-override.c - libvirt-export.c: List of auto-generated C methods, included into the libvirt-override.c method table