Is fixing the broken imports an option? If not, then yeah restoring PIL's PIL.pth is probably the best approach. We can't do this in Pillow, but it probably makes sense for Ubuntu to do it as a patch until such time as the imports can be fixed.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/1112496 Title: python-imaging broken in raring Status in “gwibber” package in Ubuntu: Confirmed Status in “phatch” package in Ubuntu: Confirmed Status in “python-imaging” package in Ubuntu: Triaged Status in “gwibber” source package in Raring: Confirmed Status in “phatch” source package in Raring: Confirmed Status in “python-imaging” source package in Raring: Triaged Bug description: python-imaging in raring doesn't include a PIL.pth to point python at the library, so attempts to import modules from the package fail with, eg: rachel@rarity:/etc$ python -m ImageMode && echo ok /usr/bin/python: No module named Image When the PIL.pth file is manually created, so python can find it, the Image module itself still fails to load: rachel@rarity:/etc$ python -m Image Traceback (most recent call last): File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main "__main__", fname, loader, pkg_name) File "/usr/lib/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/usr/lib/python2.7/dist-packages/PIL/Image.py", line 75, in <module> from . import ImageMode ValueError: Attempted relative import in non-package The ImageMode module that line seems to be trying to import, however, seems to import fine by itself: rachel@rarity:/etc$ python -m ImageMode && echo ok ok (I've confirmed that ImageMode comes from the same place, as if I remove PIL.pth again, the above line just returns the "No module named ImageMode" error) I've tried reinstalling python-imaging already. I note in any case the PIL.pth file is missing on the file list available at packages.ubuntu.com for raring. This is on Ubuntu Raring as updated from Ubuntu Quantal a few days ago: rachel@rarity:/etc$ lsb_release -rd Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 rachel@rarity:/etc$ apt-cache policy python python: Installed: 2.7.3-10ubuntu5 Candidate: 2.7.3-10ubuntu5 Version table: *** 2.7.3-10ubuntu5 0 500 http://gb.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status rachel@rarity:/etc$ apt-cache policy python-imaging python-imaging: Installed: 1.1.7+1.7.8-1ubuntu1 Candidate: 1.1.7+1.7.8-1ubuntu1 Version table: *** 1.1.7+1.7.8-1ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status Affects me as it affects building/packaging XBMC post-frodo for raring. :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/1112496/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
