Fix: Add Image.Image support to encode() overloads to resolve mypy error (#3462) #3485
+9
−8
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.
Hi @tomaarsen
In this PR I have tried #3462 by updating the
encode()method's type hints (including all relevant overload variants) to supportPIL.Image.Imageandlist[PIL.Image.Image].Summary of Changes:
ImagefromPILencode()overloads to includeImage.Imageandlist[Image.Image]encode()function signature accordinglyThis ensures that tools like
mypyno longer raise type errors when callingencode()with image inputs. As it is working correctly at inference time — the issue was limited to type checking.