# Notice: Python 3.10 support is being removed from PyTorch 2.15 (2.14 is the last release with 3.10 wheels)

**URL:** <https://dev-discuss.pytorch.org/t/notice-python-3-10-support-is-being-removed-from-pytorch-2-15-2-14-is-the-last-release-with-3-10-wheels/3440>\
**Category:** release/packaging\
**Created:** [September 16, 2026, 10:36pm UTC](https://dev-discuss.pytorch.org/t/notice-python-3-10-support-is-being-removed-from-pytorch-2-15-2-14-is-the-last-release-with-3-10-wheels/3440 "2026-09-16T22:36:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![atalman](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/atalman/32/1857_2.png) [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Post date:** [September 16, 2026, 10:36pm UTC](https://dev-discuss.pytorch.org/t/notice-python-3-10-support-is-being-removed-from-pytorch-2-15-2-14-is-the-last-release-with-3-10-wheels/3440/1 "2026-09-16T22:36:24Z")

</div>

Heads-up that **PyTorch will stop publishing Python 3.10 binaries in 2.15**. This makes **PyTorch 2.14 the last release to ship any cp310 wheels**. From 2.15, the minimum supported Python is **3.11**.

Python 3.10 is being removed from both **CD** and **CI** — no cp310 wheels or libtorch archives will be built or uploaded to PyPI or [download.pytorch.org](http://download.pytorch.org), and the 3.10 CI jobs are going away with them.

> **This starts next week.** Python 3.10 is removed from **nightly CD** during the **week of 21 September 2026** , and from **CI** on **28 September 2026**. If you install from the nightly channel, cp310 nightlies stop appearing from that date — you do not have to wait for 2.15 to be affected. Released 2.14 binaries are unaffected and stay available.

Tracking RFC: [[RFC] Remove Python 3.10 support in CI/CD · Issue #197242 · pytorch/pytorch · GitHub](https://github.com/pytorch/pytorch/issues/197242)

## Why now

Python 3.10 reaches end of life on **31 October 2026** ([Python release cycle](https://devguide.python.org/versions/)).

Our policy in [RFC-0038](https://github.com/pytorch/rfcs/blob/master/RFC-0038-cpython-support.md) is to remove during the release process of the last PyTorch release before the oldest supported Python goes EOL. PyTorch 2.15 is GA on **28 October 2026** , three days before that date, so 2.15 is that release.

This follows the same pattern as the [Python 3.9 deprecation](https://github.com/pytorch/pytorch/issues/161167) in 2.9 and the [Python 3.8 deprecation](https://github.com/pytorch/pytorch/issues/120718) before it.

## Supported Python versions

| Version | Status after 2.15 |
| --- | --- |
| **3.10** | **Dropped** |
| 3.11 | Retained (new minimum) |
| 3.12 | Retained |
| 3.13 | Retained |
| 3.14 / 3.14t | Retained |
| 3.15 / 3.15t | Retained |

The exact set of published versions changes from release to release, so check the getting-started page for the current list rather than pinning to what is written here: [https://pytorch.org/get-started/locally/](https://pytorch.org/get-started/locally/)

## If you are still on Python 3.10

**Move to 3.11 or newer.** 3.11 is supported until October 2027, so it is the smallest step that buys you a full extra year. 3.10 → 3.11 is a low-friction upgrade for most code; there are no removals in 3.11 that commonly affect PyTorch users.

If you cannot move yet, pin to 2.14 while it is current:

```auto
pip3 install torch==2.14.0 torchvision==0.29.0

```

Those binaries remain on PyPI and [download.pytorch.org](http://download.pytorch.org) indefinitely. Note that staying on 2.14 means no further bug fixes, security fixes or new features — it is a stopgap, not a destination.

Building 2.15+ from source against Python 3.10 is not supported and we will not be testing it.

## Timeline

- **2.14 (released)** — last release with published Python 3.10 wheels. These binaries remain available.
- **Week of Mon 21 September 2026** — Python 3.10 removed from **nightly CD**. No further cp310 nightlies published.
- **Mon 28 September 2026** — Python 3.10 removed from **CI**.
- **Mon 5 October 2026** — 2.15 release branch cut, with 3.10 already gone.
- **Wed 28 October 2026** — 2.15 GA, first release without Python 3.10 support.
- **Sat 31 October 2026** — Python 3.10 upstream end of life.

## Feedback

If this breaks a workflow you depend on, please comment on the RFC — [[RFC] Remove Python 3.10 support in CI/CD · Issue #197242 · pytorch/pytorch · GitHub](https://github.com/pytorch/pytorch/issues/197242) — **before the 2.15 branch cut on 5 October**. After the cut the change is in the release branch and much harder to revisit.

cc @albanD @ezyang @atalman