[PATCH] fix unicode string encoding/decoding in python bindings

[Robert McQueen]

John (J5) Palmieri wrote:
> Is that right?  c_str is typed as a char * and is not a python object.
> Does Pyrex allow this operation on char * types?  Other than that it
> looks good.

It compiles (although compiling even without my patch the generated
dbus_bindings.c has hundreds of warnings) and seems to work, both my
service and client use the python bindings at the moment, and I've fed
Arabic glyphs through and they've come out fine at the other end. I
don't see how this could happen if Pyrex wasn't boxing the char * into a
Python string object for us - I think thats the general idea.

Regards,
Rob