Mention that tobytes() with the raw encoder uses Pack.c #8878
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Alternative to #8777
In that PR, a user read https://pillow.readthedocs.io/en/stable/reference/Image.html#PIL.Image.Image.tobytes
and interpreted it as "
tobytes()will return data exactly matching Pillow's internal storage".This isn't always true for the raw encoder, and it definitely isn't true for the other encoders.
I've tried to clarify that here by updating the documentation to say that the method returns "raw image data derived from Pillow's internal storage". I've also mentioned Pack.c as the user suggested.