Description of problem:
Python 2.7 deprecated the PyCObject API in favor of a new "capsule" API.
  http://docs.python.org/dev/whatsnew/2.7.html#capsules

The deprecations are set to "ignore" by default, so in theory the API still works.

However the deprecation has caused at least one app to fail (virt-manager, see bug 620216, due to it modifying the warning settings), so I've been doublechecking the scope of usage of the PyCObject API, and am filing bugs against components that are possibly affected.

You can trigger a hard failure of the API via:
>>> import warnings
>>> warnings.filterwarnings('error')
>>> import cairo
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib64/python2.7/site-packages/cairo/__init__.py", line 1, in <module>
    from _cairo import *
PendingDeprecationWarning: The CObject type is marked Pending Deprecation in Python 2.7.  Please use capsule objects instead.
>>> dir(cairo)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'cairo' is not defined

I'm not yet sure what the best approach is to fixing this.


Version-Release number of selected component (if applicable):
pycairo-1.8.8-2.fc14.src.rpm

Grepping the prepped source tree shows these uses:
./pycairo-1.8.8/src/cairomodule.c:305:  PyModule_AddObject(m, "CAPI", PyCObject_FromVoidPtr(&CAPI, NULL));
./pycairo-1.8.8/src/pycairo.h:204:        Pycairo_CAPI = (Pycairo_CAPI_t*) PyCObject_Import("cairo", "CAPI")

Note the usage within a header file; I wonder if this leads to further knock-on effects?