[Bug 1993190] [NEW] ImportError: cannot import name '_imaging'

Tina Russell 1993190 at bugs.launchpad.net
Mon Oct 17 16:09:32 UTC 2022


Public bug reported:

If I try this:

tina at pannychis:~$ python3
Python 3.6.9 (default, Apr 18 2020, 01:56:04) 
[GCC 8.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from PIL import Image

What I would expect to happen: Image class is imported

What happens instead:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3/dist-packages/PIL/Image.py", line 69, in <module>
    from . import _imaging as core
ImportError: cannot import name '_imaging'

I’m using version 7.0.0-4ubuntu0.5 on Ubuntu 20.04.5 LTS.

What I’ve read elsewhere is that accepted practice to get around this
bug is to uninstall the apt version of Pillow and install it via pip
instead, so I assume this means the apt package has fallen behind…? (Of
course, I haven’t upgraded to Ubuntu 22.04.1 yet; is this bug fixed in
that distro version’s version of the package?)

** Affects: pillow (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pillow in Ubuntu.
https://bugs.launchpad.net/bugs/1993190

Title:
  ImportError: cannot import name '_imaging'

Status in pillow package in Ubuntu:
  New

Bug description:
  If I try this:

  tina at pannychis:~$ python3
  Python 3.6.9 (default, Apr 18 2020, 01:56:04) 
  [GCC 8.4.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> from PIL import Image

  What I would expect to happen: Image class is imported

  What happens instead:

  Traceback (most recent call last):
    File "<stdin>", line 1, in <module>
    File "/usr/lib/python3/dist-packages/PIL/Image.py", line 69, in <module>
      from . import _imaging as core
  ImportError: cannot import name '_imaging'

  I’m using version 7.0.0-4ubuntu0.5 on Ubuntu 20.04.5 LTS.

  What I’ve read elsewhere is that accepted practice to get around this
  bug is to uninstall the apt version of Pillow and install it via pip
  instead, so I assume this means the apt package has fallen behind…?
  (Of course, I haven’t upgraded to Ubuntu 22.04.1 yet; is this bug
  fixed in that distro version’s version of the package?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pillow/+bug/1993190/+subscriptions




More information about the foundations-bugs mailing list