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')
and then try to use the module (I don't have a more specific reproducer for this module yet; sorry)

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


Version-Release number of selected component (if applicable):
python-imaging-1.1.7-2.fc14.src.rpm

Grepping the source tree shows these uses of the API:
./Imaging-1.1.7/_imagingcms.c:51:  due to improper destructor setup for PyCObjects
./Imaging-1.1.7/libImaging/Imaging.h:66:/* handle magics (used with PyCObject). */
./Imaging-1.1.7/_imaging.c:2985:        return PyCObject_FromVoidPtrAndDesc(self->image, IMAGING_MAGIC, NULL);
./Imaging-1.1.7/CHANGES:497:+ Added 'getim' method, which returns a PyCObject wrapping an
./Imaging-1.1.7/PIL/Image.py:912:    # Returns a PyCObject that points to the internal image memory.
./Imaging-1.1.7/PIL/Image.py:914:    # @return A PyCObject object.
./Imaging-1.1.7/PIL/Image.py:917:        "Get PyCObject pointer to internal image memory"