Python interface and DBus

Eoin Coffey ecoffey at
Fri Jun 29 10:26:50 EDT 2007

Slighty OT:

The goal of the mono-loader project is to make libpurple (and therefore
pidgin / finch) extensible via .net languages.  Wrapping up all of libpurple
so that you can write a standalone client in .net, python, java, etc is a
bit bigger of undertaking.  So there are some difference between what I'm
currently working towards and what sascha and co. want.  Creating language
bindings is something that I'd be interested in doing post-SoC (Sascha and I
have talked about this already I think), and could really provide a lot of


PS.  Looks like SWIG stuff has already been kicked around on the wiki:

On 6/29/07, Mark Doliner <mark at> wrote:
> On Thu, 28 Jun 2007 13:27:43 -0700, Parand Darugar wrote
> > Hello,
> >
> > I'm interested in a simple interface for messaging - just the basics:
> > send/receive messages, add remove friends, etc - either in a language
> > neutral form, or in Python. I'll be using it from a web based app, so
> > no traditional UI.
> >
> > My first thought was to create a simple swig/ctypes/etc wrapper
> > around libpurple for Python, but then I ran across dbus. After a bit
> > of futzing around I have dbus working, for the most part.
> >
> > My questions are:
> > - Are there any existing Python wrappers I can use?
> >
> > - Am I better off wrapping the libpurple C API in Python or using
> > DBus? Are there any disadvantages to using DBus?
> >
> > - Anyone else interested in a no-frills Python libpurple wrapper?
> I'd think that you're better off using D-Bus.  Wrapping the libpurple C
> API in
> Python sounds like a lot of work.
> -Mark
> _______________________________________________
> Devel mailing list
> Devel at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Devel mailing list