Re: [libvirt] [PATCH 09/10] python: events: Fix C-Python handle callback prototype

2011-06-20 Thread Cole Robinson
On 06/19/2011 09:44 PM, Daniel Veillard wrote: On Wed, Jun 15, 2011 at 09:23:18PM -0400, Cole Robinson wrote: If registering our own event loop implementation written in python, any handles or timeouts callbacks registered by libvirt C code must are wrapped in a python function. There is some

Re: [libvirt] [PATCH 09/10] python: events: Fix C-Python handle callback prototype

2011-06-20 Thread Daniel Veillard
On Mon, Jun 20, 2011 at 03:26:18PM -0400, Cole Robinson wrote: On 06/19/2011 09:44 PM, Daniel Veillard wrote: On Wed, Jun 15, 2011 at 09:23:18PM -0400, Cole Robinson wrote: If registering our own event loop implementation written in python, any handles or timeouts callbacks registered by

Re: [libvirt] [PATCH 09/10] python: events: Fix C-Python handle callback prototype

2011-06-19 Thread Daniel Veillard
On Wed, Jun 15, 2011 at 09:23:18PM -0400, Cole Robinson wrote: If registering our own event loop implementation written in python, any handles or timeouts callbacks registered by libvirt C code must are wrapped in a python function. There is some argument trickery that must be :-) makes

[libvirt] [PATCH 09/10] python: events: Fix C-Python handle callback prototype

2011-06-15 Thread Cole Robinson
If registering our own event loop implementation written in python, any handles or timeouts callbacks registered by libvirt C code must are 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