[Bug 1112496] Re: python-imaging broken in raring

[Barry Warsaw]

As Rachel observes in the bug description, just adding a PIL.pth file
won't be enough.  I do not want to modify Pillow to use non-relative
imports.

What I think might work is a PILcompat.pth file and a PILcompat Python
package.  Inside there would be files like Image.py that do

from PIL import Image

(maybe with a __all__)

The thing is, I'm not sure I want 80 .py files inside PILcompat (the
number of .py files in the PIL package in Precise) even if we can
autogenerate them.  A few is not so bad though.

What other PIL packages are imported through the global namespace?  Can
anybody provide a list of those from all the rdeps?

For now, I'll play with the idea and if it works, I'll expose Image only
for now, but make it easy to add others.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to python-imaging 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 at 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 at 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 at 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 at rarity:/etc$ lsb_release -rd
  Description:	Ubuntu Raring Ringtail (development branch)
  Release:	13.04
  rachel at 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 at 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