PIL.UnidentifiedImageError: cannot identify image file (Custom installation in other directories)

[deliangyang]

What did you do?

pip install -h |grep target
#  -t, --target <dir>        Install packages into <dir>. By default this
#                            multiple platforms supported by the target
#                            abis supported by the target interpreter.

mkdir -p packages
# remove the Pillow, which installed into system packages
pip uninstall Pillow
pip install -t packages Pillow

What did you expect to happen?

It imports plugins correctly

What actually happened?

It can't import plugins, when I didn't install Pillow into system packages directories

What are your OS, Python and Pillow versions?

• OS: Debian
• Python: 3.8.0
• Pillow: All versions

The real format of the image is webp, you need to import PIL.WebPImagePlugin. The image is as follows:

from packages.PIL import Image

with open('3ae6c099102fba7a4773c3568edee0be.jpg', 'rb') as fr:
    Image.open(fr)

Traceback (most recent call last):
  File "test2.py", line 4, in <module>
    Image.open(fr)
  File "/app/packages/PIL/Image.py", line 3023, in open
    raise UnidentifiedImageError(
packages.PIL.UnidentifiedImageError: cannot identify image file <_io.BufferedReader name='3ae6c099102fba7a4773c3568edee0be.jpg'>

[radarhere]

I'm not convinced that from packages.PIL import Image is the correct thing to do after specifying a target directory, rather than continuing to use from PIL import Image.

Googling, https://stackoverflow.com/a/23435273/4093019 recognises that normal imports aren't going to work this way. https://stackoverflow.com/a/19404371/4093019 and https://stackoverflow.com/a/76161892/4093019 suggest that you add the new directory to your path.

[deliangyang]

In AWS s3 lambda, we can't run the pip command to install our packages, we have to package the dependencies with the code. As in the example above, with the dependencies in the same directory.

[homm]

@deliangyang you still can configure sys.path

[deliangyang]

Thanks, it's work. Why don't we use relative path to fix it?

[homm]

As of all other imports in PIL dir are relative, I consider absolute paths for plugins as a bug

[deliangyang]

Thank you for your time.