mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-09-18 21:51:05 +00:00
a772f4eebc
dom.getCPUStats(True, 0)
[{'cpu_time': 24699446159L, 'system_time': 10870000000L, 'user_time': 950000000L}]
dom.getCPUStats(False, 0)
[{'cpu_time': 8535292289L}, {'cpu_time': 1005395355L}, {'cpu_time': 9351766377L}, {'cpu_time': 5813545649L}]
*generator.py Add a new naming rule
*libvirt-override-api.xml The API function description
*libvirt-override.c Implement it.
|
||
|---|---|---|
| .. | ||
| 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