Hello all,
As described here [1], the upcoming python-pillow 2.2 will break "import
_imaging", and "from PIL.Image import core as _imaging" should be used
instead). This does not break backwards compatibility with python-pillow
< 2.2.
Python-pillow-2.2 will probably land in rawhide some time next weekend.
In the meantime, maintainers of packages requiring python-imaging or
python-pillow should check if this breakage affects them. The following
quick hacky script [2] shows that the following packages might need to
be adapted:
!! calibre-0:0.9.36-1.fc20.x86_64 may contain _imaging import:
usr/lib64/calibre/calibre/test_build.py: import _imaging,
_imagingmath, _imagingft
usr/lib64/calibre/calibre/test_build.py: _imaging, _imagingmath,
_imagingft
usr/lib64/calibre/calibre/test_build.py: from PIL import
_imaging, _imagingmath, _imagingft
usr/lib64/calibre/calibre/test_build.py: _imaging, _imagingmath,
_imagingft
!! python-reportlab-0:2.5-7.fc19.x86_64 may contain _imaging import:
usr/lib64/python2.7/site-packages/reportlab/lib/utils.py: for mn
in ('_rl_accel','_renderPM','sgmlop','pyRXP','pyRXPU','_imaging','Image'):
Best,
Sandro
[1] https://github.com/python-imaging/Pillow/issues/249
[2] http://smani.fedorapeople.org/scan-for-imaging.sh
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
