Repository navigation
Allow floating point constants in ImageMath operations - #10218
Merged
radarhere merged 2 commits intoOct 16, 2026
Merged
Conversation
radarhere
enabled auto-merge (squash)
October 16, 2026 07:52
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ImageMath.lambda_evalraisesTypeError: color must be int or single-element tuplewhen we add0.5to anLimage. The documentation says this should produce anFimage, so a pixel of10should become10.5.Changes proposed in this pull request:
We now create integer scalar images only for integer constants, allowing floats to use the existing promotion to mode
F.We checked the regression, both existing ImageMath suites, and the Pillow selftest.
Tested with Pillow 13.0.0.dev0 (bc7e6f5), Python 3.12.3.
— ChipLab