summaryrefslogtreecommitdiffstats
path: root/libvirt-override-api.xml
diff options
context:
space:
mode:
authorCole Robinson <crobinso@redhat.com>2011-06-15 20:02:27 -0400
committerCole Robinson <crobinso@redhat.com>2011-06-21 10:08:48 -0400
commit12d8d49559c2c4616357dd1d99cd7bcd39646033 (patch)
tree4131ea598e3db08a0782f6b71587bd090d6f69e8 /libvirt-override-api.xml
parente46bf585a6ff8f535c0bccb1667fafd0aebd1904 (diff)
downloadlibvirt-python-v6-12d8d49559c2c4616357dd1d99cd7bcd39646033.tar.gz
libvirt-python-v6-12d8d49559c2c4616357dd1d99cd7bcd39646033.tar.xz
libvirt-python-v6-12d8d49559c2c4616357dd1d99cd7bcd39646033.zip
python: events: Fix C->Python handle callback prototype
If registering our own event loop implementation written in python, any handles or timeouts callbacks registered by libvirt C code must be wrapped in a python function. There is some argument trickery that makes this all work, by wrapping the user passed opaque value in a tuple, along with the callback function. Problem is, the current setup requires the user's event loop to know about this trickery, rather than just treating the opaque value as truly opaque. Fix this in a backwards compatible manner, and adjust the example python event loop to do things the proper way.
Diffstat (limited to 'libvirt-override-api.xml')
0 files changed, 0 insertions, 0 deletions