If removal version has arrived, raise an error #84
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.
An idea for python-pillow#6184. Feel free to disregard if you want, as it is rather theoretical.
What if we managed to accidentally leave in a Pillow 10 deprecation warning for the Pillow 10 release?
Users would then be told that the feature would be removed in Pillow 10, with a date in the past, which would introduce confusion.
Or worse, we might have removed the
when == 10
condition, and they would receive a ValueError.Instead, we could switch to the generic statement that it would be removed in "a future version".