delta/libvirt-python.git, branch v3.3.0

Release of libvirt-python-3.3.0

2017-05-05T19:48:36+00:00

event-test: add ability to run the asyncio event loop

2017-04-04T14:28:50+00:00

The event test program '--loop' arg is modified to take the name
of an event loop impl to run. eg 'event-test.py --loop asyncio'

Signed-off-by: Daniel P. Berrange

event-test: rename example event loop impl

2017-04-04T14:28:50+00:00

Use the name 'Poll' instead of 'Pure' for the event loop demo,
since there's now a second pure python loop impl available.

Signed-off-by: Daniel P. Berrange

event-test: unregister callbacks & close conn on exit

2017-04-04T14:28:50+00:00

In order to test cleanup code paths we must unregister all callbacks
and close the connection on shutdown. Since cleanup happens in the
background, we do a short sleep to allow the main loop to run its
cleanup too.

Signed-off-by: Daniel P. Berrange

event-test: add timeout to exit event loop

2017-04-04T14:28:50+00:00

Signed-off-by: Daniel P. Berrange

event-test: free opaque data when removing callbacks

2017-04-04T14:28:50+00:00

The pure python event loop impl has to call

  libvirt.virEventInvokeFreeCallback

to free the event opaque data from a clean stack context

Signed-off-by: Daniel P. Berrange

Add asyncio event loop implementation

2017-04-04T14:28:50+00:00

This is usable only on python >= 3.4 (or 3.3 with out-of-tree asyncio),
however it should be harmless for anyone with older python versions.

In simplest case, to have the callbacks queued on the default loop:

    >>> import libvirtaio
    >>> libvirtaio.virEventRegisterAsyncIOImpl()

The function is not present on non-compatible platforms.

Signed-off-by: Wojtek Porczyk

Allow for ff callbacks to be called by custom event implementations

2017-04-04T14:00:27+00:00

The documentation says:
> If the opaque user data requires free'ing when the handle is
> unregistered, then a 2nd callback can be supplied for this purpose.
> This callback needs to be invoked from a clean stack. If 'ff'
> callbacks are invoked directly from the virEventRemoveHandleFunc they
> will likely deadlock in libvirt.

And they did deadlock. In removeTimeout too. Now we supply a custom
function to pick it from the opaque blob and fire.

Signed-off-by: Wojtek Porczyk 
Signed-off-by: Daniel P. Berrange

Release of libvirt-python-3.2.0

2017-04-02T15:08:59+00:00

* setup.py: bumped version

event: Add handler for block threshold event

2017-03-29T14:59:39+00:00

Unfortunately python doesn't generate those.