[cairo] pycairo status?

Bryce Harrington bryce at osg.samsung.com
Thu Aug 14 11:50:58 PDT 2014

On Thu, Aug 14, 2014 at 01:58:15PM -0400, Behdad Esfahbod wrote:
> On 14-08-14 01:29 PM, Dave Curtis wrote:
> > On 08/14/2014 09:26 AM, Behdad Esfahbod wrote:
> >> On 14-08-14 12:39 AM, Dave Curtis wrote:
> >>> Are they being actively maintained?
> >>
> >> No. :(
> > 
> > It isn't clear to me exactly how far behind pycairo and py2cairo have fallen?
> I know, for example, that the mesh gradients are not in there.  I'm guessing
> that neither are cairo_device_t, recording-surface, and probably some egl stuff?

Right, it's like 2 full releases behind.

> > Also, do the Python bindings need to be rev'ed for each release of cairo, or
> > can libcairo move forward without disturbing the pycairo bindings?
> No, the API that is there keeps working.  It's just newer API that is missing.
> > And is
> > there some difficult technical problem that causes the python2 bindings and
> > the python3 bindings to be in separate modules instead of a single
> > version-aware module?
> I *think* CPython API has changed enough that one binary wouldn't do, but one
> source should be possible?

There is another python cairo binding called cairocffi, which I gather
is a bit more up to date (I haven't tried it myself).  It claims to be a
drop-in replacement for pycairo.


Anyone know anything more about it?


More information about the cairo mailing list