-
-
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
Cannot import ImageCms with no LITTLECMS2 feature installed #8193
Comments
Yes, you are right this was unintentional. I've created #8196 to fix it. |
Ran into this today it still appears to be an issue when building from main on windows without lcms2 present. edit: made a patch for my build to pass without adding the |
Looks like we're waiting on resolution to a Docs build issue in order to merge the fix(s). |
This is the same as proposed fix #8196 |
Both #8196 and #8197 fix the problem, it's just a matter of somebody (I guess @radarhere or @hugovk) to decide which one to use. |
I'm not entirely sure about the priority level of building docs without dependencies (Pillow is a library first and foremost, has public online documentation, and has distributed documentation as a bonus feature), but I've found that just using |
@radarhere - thanks for the fix! From my perspective (which admittedly may not be that relevant here) your fix is the cleaner approach, and I see no reason not to merge it. |
The opinion of Pillow users should always be relevant. Thanks for your review - just waiting for approval from another member of the core team. |
If building pillow without the LITTLECMS2 feature (e.g. with the lcms library not present), it was still possible to import
ImageCms
until pillow 10.2. This is done by usingDeferredError
:With the type hints added in 10.3, there is now a top level access to
_imagingcms
aliascore
:Using
causes now (in 10.3/10.4):
Happens both under Windows (as shown) and Linux.
This is probably a fringe problem, but can easily be fixed by using the string version of the problematic type hint:
Environment:
Features:
The text was updated successfully, but these errors were encountered: