-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Drop support for Python 3.9 #9119
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
Conversation
Upgraded in python-pillow/docker-images#244 🚀 |
# M1 only available for 3.10+ | ||
- { os: "macos-13", python-version: "3.9" } | ||
exclude: | ||
- { os: "macos-latest", python-version: "3.9" } |
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.
Just to be clear, so you'd like to drop testing for Intel macOS with each PR? We're still generating wheels for the platform, so we should still pick up any problems sooner or later.
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.
GitHub Actions will be soon dropping macos-13
aka Intel:
The macOS 13 hosted runner image is closing down, following our N-1 OS support policy. This process will begin September 1, 2025, and the image will be fully retired on November 14, 2025. We recommend updating workflows to use macos-14 or macos-15.
So we'll need to drop it at some point. But I've pushed a commit to keep it for now (with 3.10), finding problems sooner is better than later :)
At some point, we'll have to decide how long we want to support Intel, and this doesn't necessarily need to be as long as Apple does.
At WWDC 2025 on June 9, 2025, Apple announced that macOS Tahoe would be the last release of macOS that would support Intel Macs, with macOS 27 in 2026 being exclusive to Macs with Apple silicon.
https://en.wikipedia.org/wiki/Mac_transition_to_Apple_silicon#2025
macOS 26 Tahoe will be released later this year and will likely be supported for three years, until late 2028.
We've generally followed upstream OS support timelines, but test and CI availability also influences ease of maintenance and support. Especially for building wheels. Perhaps we can test via emulation, or have best effort without main CI/wheels so people can self-build, or drop it. Let's see.
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.
I've created #9212
Python 3.9 reaches end of life in October 2025:
Pillow 12.0.0 is planned for 2025-10-15 and will drop Python 3.9:
Notes:
Only Python 3.9 is available for Cygwin. I don't see any news of upgrades in recent months on the mailing list. This means we need to drop the Cygwin testing from the CI. I've not removed Python/C/test code for Cygwin, we can decide separately if/when to remove that.
We'll have to decide whether to drop or upgrade the Docker images for Amazon 2 (EOL 2026-06-30), Amazon 2023 (2029-06-30) and CentOS Stream 9 (2027-05-31) from Python 3.9 to something newer. We test CentOS Stream 10 (2030-01-01) with Python 3.12.
Qt typing refactoring: we can use
a | b
instead ofUnion[a, b]
with Python 3.10. But mypy didn't like that for the Qt declarations, so we can instead use the imported ones with# type: ignore[assignment]
and removetype: ignore[operator]
elsewhere.