Re: [Gegl-developer] Returning to python-gegl



So it looks like the right-thing-to-do now is to add introspection
to Babl (otherwise we will need dirty workarounds in gegl).

  js
 -><-

On 12 February 2015 at 21:01,  <jcupitt gmail com> wrote:
On 12 February 2015 at 16:30, Joao S. O. Bueno <gwidion mpc com br> wrote:
Otherwise, I think I will rewire the python bindings using another
method to bridge to the C library, which is more predictive and better
supported.

I've made a Python binding for my largish C library using
gobject-introspection and not had any serious problems. It was a bit
wonky a year or so ago, but it honestly seems OK now. Performance is
good too, and I don't see any memory leaks. I'm very grateful for it.

I've been trying to make a Ruby binding in the same way and oh dear oh
dear it's a lot harder :(

John


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]