You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@khazhyk Can you send a pull request with the changes you want? Also what platform did you install on? I know that if you compile Pillow you'll see webp missing… but maybe you installed a pre-built wheel.
I had installed (not from wheel) a while ago and just so happened to recently to start using webp.
From what I understand by the code, a plugin will fail to import (and register) if the native extension isn't compiled (and logs to debug), which means by the time we reach open() we can't distinguish between something that matches no plugins and something that would match a plugin if it's native portion had been compiled. It seems like that could be changed to allow for that, although I don't fully understand PIL's design or rationale for what implications that would have.
What did you do?
Tried to open a webp file.
What did you expect to happen?
The webp file opened, or PIL would notify me that it was compiled without webp support.
What actually happened?
Got generic 'OSError: cannot identify image file'
What versions of Pillow and Python are you using?
Python 3.5, Pillow 3.4.2
Judging by #1930 a more specific error doesn't seem unreasonable, and could speed up troubleshooting for others in the future.
The text was updated successfully, but these errors were encountered: