-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Closed
Labels
module: ciRelated to continuous integrationRelated to continuous integrationmodule: deprecationtriagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module
Milestone
Description
Similar to #120718
After addition of Python 3.14 to CD, CI to be completed.
We want to start process for deprecation of Python 3.9 from Pytorch CI and nightly builds.
End of Life for Python 3.9 is October 2025 Please see: https://devguide.python.org/versions/
According to our policy: According to our policy: https://github.com/pytorch/rfcs/blob/master/RFC-0038-cpython-support.md :
- Deprecate during the release process of the last PyTorch release before the oldest version of python goes EOL.
Hence we have following two options:
Option 1
Deprecate Python 3.9 for Release 2.10:
| Feature | Target Date |
|---|---|
| Deprecate Python 3.9 from nightly CD | Sept 2025 |
| Deprecate Python 3.9 from nightly CI | Sept/Oct 2025 |
| Release PyTorch 2.9 with Python 3.9 support. Announce deprecation of Python 3.9 for next Release | Oct 2025 |
| Release PyTorch 2.10 without Python 3.9 support | Jan 2026 |
Option 2 - Will be implementing this option, as per discussion @malfet and @albanD
Deprecate Python 3.9 for Release 2.9:
| Feature | Target Date |
|---|---|
| Announce Python 3.9 deprecation | Aug 2025 |
| Deprecate Python 3.9 from nightly CD | Aug 2025 |
| Deprecate Python 3.9 from nightly CI | Aug 2025 |
| Release PyTorch 2.9 without Python 3.9 support | Oct 2025 |
cc @malfet @seemethere @pytorch/pytorch-dev-infra @albanD @ezyang
Versions
2.10
akihironitta
Metadata
Metadata
Assignees
Labels
module: ciRelated to continuous integrationRelated to continuous integrationmodule: deprecationtriagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module
Type
Projects
Status
Done