Warn that tobytes is not for compressed image data #1470
Merged
Conversation
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
It probably isn't what most developers want.
Member
|
Thanks for that. I've reworded it a bit and merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Every time I try to get in-memory PNG or JPEG data I tend to spend half an hour fighting with tobytes until I remember it is not going to work and I'm supposed to use
im.save(fp, format='png').#985 makes me think I'm not alone, and a clear warning in the documentation can only help others (and future-me).
I don't actually know what tobytes is for, so I went with something along the lines of @wiredfool's comment in #985, they note that it's