-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin mechanism is not working as in PIL 1.1.7 #404
Comments
There were several reasons that change was made, and documentation would help. If you've got the proper registration function calls in your file, simply importing it should be enough. |
wiredfool
added a commit
to wiredfool/Pillow
that referenced
this issue
Nov 13, 2013
… plugin not found
aclark4life
added a commit
that referenced
this issue
Nov 29, 2013
Docs: Noted import change for Image Plugins. Fixes #404, plugin not foun...
radarhere
pushed a commit
to radarhere/Pillow
that referenced
this issue
Sep 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that the mechanism to extend Image plugins is different in Pillow.
With PIL 1.1.7 I wrote my own image plugin, that I would call xxxImagePlugin.py
The code in that plugin would ´register´ the extension of my new Image format, say ´xxx´.
I would call Image.open(´myfile.xxx´) and there I had it.
Now, _plugins[] is initialized in init.py and there seems to be no further checking of the new image formats.
Interactively, I was able to modify the source and reload it, to observe changes as I was developing it, whereas now the _plugins is obscured in the namespacing convention...
It may make sense this change, but should be documented more clearly
The text was updated successfully, but these errors were encountered: