-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update "What about PIL?" section #7861
Conversation
PyPI moderators gave PIL project to Pillow team in January 2020
It seems Scenario 3 at https://www.webaxe.org/strikethrough-html-accessibility/ is one workaround -- also add a Or scenario 4, but there's some gotchas mentioned there too. It might be better to rewrite/revise the text instead? |
I'll redo with the suggestions from https://www.webaxe.org/strikethrough-html-accessibility/, thanks! |
I'd prefer rewriting so instead the text is up-to-date, rather than asking our users to read then mentally discard the outdated info. The "As time passes..." sentence is also no longer relevant. |
Co-authored-by: Ondrej Baranovič <nulano@nulano.eu>
OK rewrite it is. I merged @nulano 's commit and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Maybe also add a note to the end that the PIL project on PyPi will be left as it is, and will not be updated to have the Pillow code? |
And update this from "Why a fork?" -Also, PIL's current bi-yearly (or greater) release schedule is too infrequent to accommodate the large number and frequency of issues reported.
+Also, PIL's bi-yearly (or greater) release schedule was too infrequent to accommodate the large number and frequency of issues reported. |
|
for more information, see https://pre-commit.ci
PyPI moderators gave PIL project to Pillow team in January 2020
Related to #1535 .
Changes proposed in this pull request: