On Tue, Jul 1, 2008 at 15:39, Yann Leboulanger <[EMAIL PROTECTED]> wrote:
> Wow cool ! We unfortunatly don't have much time now because we'd like to
> release very very soon, but that would be very cool to finalize that. What
> are you plans about those bindings? Do you think to send them to author so
> that he can release them? Do you think to start new project to them?
> But for sure it's interesting as it's the only async python module that
> allows AAAA resolution.
I worked on it since my last mail, and I now have a clean module which
doesn't use swig. It's a pure C/python module, with correct classes.
The only missing part is error/exception handling, but it's fully
I even replaced the resolver in the gajim code by a small wrapper and
it's working well.
I'd like to test the case here, the only case where there is a problem
for me is with a google talk account (doesn't seems to use the
resolver, is this the issue?). I didn't try AAAA resolution either,
does anyone have a usecase?
I discovered a small bug in libasyncns and I sent a mail to Lennart
Poettering about it, but didn't get any reply.
So I was planning to release it on my own, it's always possible to
include it later in libasyncns if we want to.
Other python bindings have a separate project (e.g. adns-python for
adsn), so it's not uncommon to do it this way.
I'll try to upload the binding today (I plan to host it on launchpad
since I'm mainly using bzr), even if it's not yet stable.
(I'm posting from another mail address, because the webmail of my main
one is buggy as hell and break mailing-lists threading (and maybe
Gajim-devel mailing list