# Latest

**URL:** https://dev-discuss.pytorch.org/latest.md

[Latest](https://dev-discuss.pytorch.org/latest.md) · [Categories](https://dev-discuss.pytorch.org/categories.md)

---

## [Welcome to PyTorch Dev Forums](https://dev-discuss.pytorch.org/t/welcome-to-pytorch-dev-forums/7)

<div class="topic-metadata">

**Author:** [@system](https://dev-discuss.pytorch.org/u/system)\
**Replies:** 0\
**Last updated:** [January 22, 2021, 3:48pm UTC](https://dev-discuss.pytorch.org/t/welcome-to-pytorch-dev-forums/7 "2021-01-22T15:48:15Z")

</div>

These forums are used by the core developers and contributors to the PyTorch codebase. They are used as long-form communication focused on technical discussions, as opposed to reporting issues (on github) or short-form …

---

## [Workflows never approved — pytorch/pytorch PR #194438 (docs only)](https://dev-discuss.pytorch.org/t/workflows-never-approved-pytorch-pytorch-pr-194438-docs-only/3435)

<div class="topic-metadata">

**Author:** [@pandeylakshya207-max](https://dev-discuss.pytorch.org/u/pandeylakshya207-max)\
**Replies:** 2\
**Last updated:** [September 23, 2026, 8:30pm UTC](https://dev-discuss.pytorch.org/t/workflows-never-approved-pytorch-pytorch-pr-194438-docs-only/3435 "2026-09-23T20:30:21Z")

</div>

Hi all, I opened PR #194438 two weeks ago — a docs-only change adding an explanation of the adaptive pooling bin-boundary algorithm (addressing a long-standing FIXME in torch/nn/modules/pooling.py). No source code is mo…

---

## [Removing CUDA 13.0 builds from PyTorch CI/CD, starting the week of Sept 28](https://dev-discuss.pytorch.org/t/removing-cuda-13-0-builds-from-pytorch-ci-cd-starting-the-week-of-sept-28/3447)

<div class="topic-metadata">

**Author:** [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Replies:** 0\
**Last updated:** [September 23, 2026, 8:29pm UTC](https://dev-discuss.pytorch.org/t/removing-cuda-13-0-builds-from-pytorch-ci-cd-starting-the-week-of-sept-28/3447 "2026-09-23T20:29:35Z")

</div>

TL;DR — Starting the week of Monday, Sept 28 2026, we are removing CUDA 13.0 from the PyTorch nightly build matrix and CI. Nightly CUDA builds will be 13.2 (stable / default) and 13.4 (prototype). No GPU architecture sup…

---

## [PyTorch Release 2.14.1](https://dev-discuss.pytorch.org/t/pytorch-release-2-14-1/3444)

<div class="topic-metadata">

**Author:** [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Replies:** 0\
**Last updated:** [September 22, 2026, 6:13pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-14-1/3444 "2026-09-22T18:13:11Z")

</div>

Hi everyone, We are going to be releasing PyTorch 2.14.1, a patch release for the 2.14 line, following the usual patch release process. Milestones Milestone Description Date M1 Patch Release Announcement Septem…

---

## [\[RFC-0036\] Zero-GC 64-Byte Cache-Aligned Flat Arena for Speculative Decoding Verification](https://dev-discuss.pytorch.org/t/rfc-0036-zero-gc-64-byte-cache-aligned-flat-arena-for-speculative-decoding-verification/3441)

<div class="topic-metadata">

**Author:** [@markbgilbert](https://dev-discuss.pytorch.org/u/markbgilbert)\
**Replies:** 0\
**Last updated:** [September 21, 2026, 4:26pm UTC](https://dev-discuss.pytorch.org/t/rfc-0036-zero-gc-64-byte-cache-aligned-flat-arena-for-speculative-decoding-verification/3441 "2026-09-21T16:26:22Z")

</div>

We have submitted RFC-0036: Zero-GC 64-Byte Cache-Aligned Flat Arena Runtime to address host-side CPU overhead and allocator contention in high-throughput LLM speculative decoding and batch token ingestion. Empirical Pr…

---

## [Notice: Python 3.10 support is being removed from PyTorch 2.15 (2.14 is the last release with 3.10 wheels)](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)

<div class="topic-metadata">

**Author:** [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Replies:** 0\
**Last updated:** [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")

</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 f…

---

## [PyTorch Release 2.15 | Key Dates](https://dev-discuss.pytorch.org/t/pytorch-release-2-15-key-dates/3434)

<div class="topic-metadata">

**Author:** [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Replies:** 1\
**Last updated:** [September 11, 2026, 8:20am UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-15-key-dates/3434 "2026-09-11T08:20:47Z")

</div>

We are excited to announce the start of the PyTorch 2.15 release cycle and look forward to all the great contributions from our community. For 2.15 we are keeping the branch-cut → release window at ~3 weeks: the release…

---

## [Notice: CUDA 12.6 wheels will no longer be published from PyTorch 2.15 (drops Maxwell / Pascal / Volta)](https://dev-discuss.pytorch.org/t/notice-cuda-12-6-wheels-will-no-longer-be-published-from-pytorch-2-15-drops-maxwell-pascal-volta/3432)

<div class="topic-metadata">

**Author:** [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Replies:** 0\
**Last updated:** [September 4, 2026, 3:13pm UTC](https://dev-discuss.pytorch.org/t/notice-cuda-12-6-wheels-will-no-longer-be-published-from-pytorch-2-15-drops-maxwell-pascal-volta/3432 "2026-09-04T15:13:08Z")

</div>

Heads-up that PyTorch will stop publishing CUDA 12.6 binaries in 2.15. Since CUDA 12.8 and 12.9 were already dropped, this means PyTorch 2.14 is the last release to ship any CUDA 12.x wheels. From 2.15, CUDA 12.6 is a bu…

---

## [PyTorch 2.14.0 General Availability](https://dev-discuss.pytorch.org/t/pytorch-2-14-0-general-availability/3431)

<div class="topic-metadata">

**Author:** [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Replies:** 2\
**Last updated:** [September 2, 2026, 11:00pm UTC](https://dev-discuss.pytorch.org/t/pytorch-2-14-0-general-availability/3431 "2026-09-02T23:00:59Z")

</div>

We are excited to announce the release of PyTorch® 2.14. All the binaries have been published to PyPI and download.pytorch.org. Installation instructions for the new release can be found at the familiar getting started p…

---

## [Fork PR workflow approval: no escalation path when reviewer pings go unanswered](https://dev-discuss.pytorch.org/t/fork-pr-workflow-approval-no-escalation-path-when-reviewer-pings-go-unanswered/3430)

<div class="topic-metadata">

**Author:** [@tolleybot](https://dev-discuss.pytorch.org/u/tolleybot)\
**Replies:** 0\
**Last updated:** [August 29, 2026, 7:43pm UTC](https://dev-discuss.pytorch.org/t/fork-pr-workflow-approval-no-escalation-path-when-reviewer-pings-go-unanswered/3430 "2026-08-29T19:43:36Z")

</div>

Hi all, I’d like to ask about the workflow approval step for fork PRs, specifically what a contributor should do when the documented path does not produce a result. The documented path. When a ciflow label is applied t…

---

## [PyTorch 2.14 Final RC Available](https://dev-discuss.pytorch.org/t/pytorch-2-14-final-rc-available/3429)

<div class="topic-metadata">

**Author:** [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Replies:** 0\
**Last updated:** [August 27, 2026, 4:53pm UTC](https://dev-discuss.pytorch.org/t/pytorch-2-14-final-rc-available/3429 "2026-08-27T16:53:51Z")

</div>

The final 2.14.0 RC for PyTorch is available for download from the pytorch-test channel. Remaining Key Dates Milestones M1 through M4 are complete. M4.1: Tutorial drafts submission deadline (28/8/26) M5: External-Faci…

---

## [What is the correct, future-proof, way of deploying a pytorch python model in C++ for inference?](https://dev-discuss.pytorch.org/t/what-is-the-correct-future-proof-way-of-deploying-a-pytorch-python-model-in-c-for-inference/2775)

<div class="topic-metadata">

**Author:** [@raphael10-collab](https://dev-discuss.pytorch.org/u/raphael10-collab)\
**Replies:** 27\
**Last updated:** [August 27, 2026, 2:14pm UTC](https://dev-discuss.pytorch.org/t/what-is-the-correct-future-proof-way-of-deploying-a-pytorch-python-model-in-c-for-inference/2775 "2026-08-27T14:14:27Z")

</div>

Hi! I want to understand if it is possible, and how to do it, to deploy and use for inference in C++, pytorch models developed, and trained in python From here : Pytorch 2 and the c++ interface - #6 by ezyang - C++ - P…

---

## [Core Maintainer Meeting April 17th](https://dev-discuss.pytorch.org/t/core-maintainer-meeting-april-17th/3345)

<div class="topic-metadata">

**Author:** [@gottbrath](https://dev-discuss.pytorch.org/u/gottbrath)\
**Replies:** 1\
**Last updated:** [August 25, 2026, 4:15pm UTC](https://dev-discuss.pytorch.org/t/core-maintainer-meeting-april-17th/3345 "2026-08-25T16:15:22Z")

</div>

The next PyTorch core maintainer meeting will be held April 17th The general purpose of these meetings is to: Discuss any technical plans and roadmaps for PyTorch Review any high-level requests related to PyTorch, suc…

---

## [PyTorch Core Maintainer Meeting - Aug 21st](https://dev-discuss.pytorch.org/t/pytorch-core-maintainer-meeting-aug-21st/3424)

<div class="topic-metadata">

**Author:** [@gottbrath](https://dev-discuss.pytorch.org/u/gottbrath)\
**Replies:** 1\
**Last updated:** [August 20, 2026, 6:17pm UTC](https://dev-discuss.pytorch.org/t/pytorch-core-maintainer-meeting-aug-21st/3424 "2026-08-20T18:17:16Z")

</div>

The next PyTorch core maintainer meeting will be held Aug 21st The general purpose of these meetings is to: Discuss any technical plans and roadmaps for PyTorch Review any high-level requests related to PyTorch, such …

---

## [Reminder — Call for Features: PyTorch 2.14](https://dev-discuss.pytorch.org/t/reminder-call-for-features-pytorch-2-14/3423)

<div class="topic-metadata">

**Author:** [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Replies:** 0\
**Last updated:** [August 14, 2026, 8:51pm UTC](https://dev-discuss.pytorch.org/t/reminder-call-for-features-pytorch-2-14/3423 "2026-08-14T20:51:48Z")

</div>

Hi everyone, This is a reminder to feature owners to file a release-highlight issue for every feature you want tracked in the 2.14 release. IMPORTANT: features that are not submitted will NOT be mentioned in the releas…

---

## [PyTorch 2.14 RC1 produced for pytorch & torchvision](https://dev-discuss.pytorch.org/t/pytorch-2-14-rc1-produced-for-pytorch-torchvision/3422)

<div class="topic-metadata">

**Author:** [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Replies:** 0\
**Last updated:** [August 13, 2026, 4:10pm UTC](https://dev-discuss.pytorch.org/t/pytorch-2-14-rc1-produced-for-pytorch-torchvision/3422 "2026-08-13T16:10:39Z")

</div>

The core binaries are now available for download and testing on pytorch test channel. Here is the 2.14 release issue tracker for cherry pick submissions. Reminder of Key Dates Milestones M1 through M3 are complete. M…

---

## [Improving PyTorch performance by hinting the Python GC about unreachable cycles](https://dev-discuss.pytorch.org/t/improving-pytorch-performance-by-hinting-the-python-gc-about-unreachable-cycles/3421)

<div class="topic-metadata">

**Author:** [@omripalmon](https://dev-discuss.pytorch.org/u/omripalmon)\
**Replies:** 0\
**Last updated:** [August 12, 2026, 5:51am UTC](https://dev-discuss.pytorch.org/t/improving-pytorch-performance-by-hinting-the-python-gc-about-unreachable-cycles/3421 "2026-08-12T05:51:16Z")

</div>

I have recently tried to convince the Python community to add a feature to the Python GC which would accept hints that a certain group of objects is unreachable and can be deallocated. Such a feature would reduce the amo…

---

## [PyTorch Release 2.14 Branch Cut is Complete](https://dev-discuss.pytorch.org/t/pytorch-release-2-14-branch-cut-is-complete/3420)

<div class="topic-metadata">

**Author:** [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Replies:** 0\
**Last updated:** [August 11, 2026, 7:23pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-14-branch-cut-is-complete/3420 "2026-08-11T19:23:26Z")

</div>

Hello everyone, This is to confirm that the PyTorch 2.14 release branch cut is now complete. You can find the branch here and the issue tracker here. Ask: Please review the state of the branch as well as CI/CD. Also, p…

---

## [Contributing as a beginner](https://dev-discuss.pytorch.org/t/contributing-as-a-beginner/3003)

<div class="topic-metadata">

**Author:** [@Hummd](https://dev-discuss.pytorch.org/u/Hummd)\
**Replies:** 3\
**Last updated:** [August 10, 2026, 2:37pm UTC](https://dev-discuss.pytorch.org/t/contributing-as-a-beginner/3003 "2026-08-10T14:37:31Z")

</div>

Hi guys, I would like to be a contributor, but I am new to OS. I am good with python and can pick things up quickly. Is there an issue I can work on ideally would love to work with someone if possible! Really eager to le…

---

## [PRs stuck for 2 months, for MPS perf](https://dev-discuss.pytorch.org/t/prs-stuck-for-2-months-for-mps-perf/3416)

<div class="topic-metadata">

**Author:** [@qwertey6](https://dev-discuss.pytorch.org/u/qwertey6)\
**Replies:** 3\
**Last updated:** [August 3, 2026, 4:42pm UTC](https://dev-discuss.pytorch.org/t/prs-stuck-for-2-months-for-mps-perf/3416 "2026-08-03T16:42:03Z")

</div>

Two MPS perf PRs have been done and green for a few weeks but I can’t get eyes on them: PR #184780 (unique): native Metal kernel replacing the MPSGraph scatter path. ~12,000x perf improvement, and closes issues: #97310 …

---

## [Early Contribution](https://dev-discuss.pytorch.org/t/early-contribution/3419)

<div class="topic-metadata">

**Author:** [@chinu0609](https://dev-discuss.pytorch.org/u/chinu0609)\
**Replies:** 0\
**Last updated:** [August 3, 2026, 2:50pm UTC](https://dev-discuss.pytorch.org/t/early-contribution/3419 "2026-08-03T14:50:38Z")

</div>

Hi! I’m interested in contributing to PyTorch, but I noticed that most of the good first issues already have open PRs. I’m looking for a beginner-friendly work that can be done. Could anyone help me with that

---

## [Review request: enable flake8-bugbear B007 repo-wide (PR #189319, tracking issue #106571)](https://dev-discuss.pytorch.org/t/review-request-enable-flake8-bugbear-b007-repo-wide-pr-189319-tracking-issue-106571/3418)

<div class="topic-metadata">

**Author:** [@HumphreySun98](https://dev-discuss.pytorch.org/u/HumphreySun98)\
**Replies:** 0\
**Last updated:** [July 31, 2026, 5:31am UTC](https://dev-discuss.pytorch.org/t/review-request-enable-flake8-bugbear-b007-repo-wide-pr-189319-tracking-issue-106571/3418 "2026-07-31T05:31:12Z")

</div>

Hi all, I have a lint-enablement PR that has been merge-ready for ~3 weeks but can’t find a reviewer, likely because it crosses many module boundaries. Posting here as suggested escalation before considering splitting i…

---

## [Guidance requested on stalled PR adding pivoted QR decomposition](https://dev-discuss.pytorch.org/t/guidance-requested-on-stalled-pr-adding-pivoted-qr-decomposition/3318)

<div class="topic-metadata">

**Author:** [@thkloss](https://dev-discuss.pytorch.org/u/thkloss)\
**Replies:** 2\
**Last updated:** [July 24, 2026, 6:43am UTC](https://dev-discuss.pytorch.org/t/guidance-requested-on-stalled-pr-adding-pivoted-qr-decomposition/3318 "2026-07-24T06:43:18Z")

</div>

Hi all, I am looking for guidance regarding a PR I opened that adds pivoted QR decomposition to ATen and torch.linalg: PR: Add pivoted QR decomposition to ATen and torch.linalg by thkloss · Pull Request #170051 · pytor…

---

## [PyTorch Release 2.14 | Key Dates](https://dev-discuss.pytorch.org/t/pytorch-release-2-14-key-dates/3417)

<div class="topic-metadata">

**Author:** [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Replies:** 0\
**Last updated:** [July 21, 2026, 2:54pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-14-key-dates/3417 "2026-07-21T14:54:02Z")

</div>

We are excited to announce the start of the \*\*PyTorch 2.14\*\* release cycle and look forward to all the great contributions from our community. For 2.14 we are shortening the \*\*branch-cut → release\*\* window to \*\*~3 weeks…

---

## [Meta PyTorch Team 2026 H2 Roadmaps](https://dev-discuss.pytorch.org/t/meta-pytorch-team-2026-h2-roadmaps/3415)

<div class="topic-metadata">

**Author:** [@dcci](https://dev-discuss.pytorch.org/u/dcci)\
**Replies:** 0\
**Last updated:** [July 20, 2026, 4:14pm UTC](https://dev-discuss.pytorch.org/t/meta-pytorch-team-2026-h2-roadmaps/3415 "2026-07-20T16:14:10Z")

</div>

The Meta PyTorch team is happy to share our 2026 H2 roadmap!

---

## [Heads-up: PyTorch's build is switching from setuptools to scikit-build-core, and setup.py goes away](https://dev-discuss.pytorch.org/t/heads-up-pytorchs-build-is-switching-from-setuptools-to-scikit-build-core-and-setup-py-goes-away/3414)

<div class="topic-metadata">

**Author:** [@zklaus](https://dev-discuss.pytorch.org/u/zklaus)\
**Replies:** 0\
**Last updated:** [July 13, 2026, 7:29pm UTC](https://dev-discuss.pytorch.org/t/heads-up-pytorchs-build-is-switching-from-setuptools-to-scikit-build-core-and-setup-py-goes-away/3414 "2026-07-13T19:29:32Z")

</div>

Next Monday Jul 20, 2026, PyTorch’s build backend switches from setuptools to scikit-build-core 1.0, and setup.py is removed. TL;DR: If you build with spin or pip install (regular or editable), nothing changes. If you…

---

## [Workflows never approved for a week — pytorch/pytorch PR #188945](https://dev-discuss.pytorch.org/t/workflows-never-approved-for-a-week-pytorch-pytorch-pr-188945/3413)

<div class="topic-metadata">

**Author:** [@Partha-Shankar](https://dev-discuss.pytorch.org/u/Partha-Shankar)\
**Replies:** 0\
**Last updated:** [July 12, 2026, 11:41am UTC](https://dev-discuss.pytorch.org/t/workflows-never-approved-for-a-week-pytorch-pytorch-pr-188945/3413 "2026-07-12T11:41:33Z")

</div>

Hi, I’m an external contributor. My PR #188945 was triaged and labeled module: numpy about a week ago (by @drisspg), with cc @mruberry @rgommers auto-added. Since then, the CI workflows are still showing “awaiting approv…

---

## [PyTorch 2.13.0 General Availability](https://dev-discuss.pytorch.org/t/pytorch-2-13-0-general-availability/3412)

<div class="topic-metadata">

**Author:** [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Replies:** 0\
**Last updated:** [July 8, 2026, 8:00pm UTC](https://dev-discuss.pytorch.org/t/pytorch-2-13-0-general-availability/3412 "2026-07-08T20:00:22Z")

</div>

We are excited to announce the release of PyTorch® 2.13. All the binaries have been published to PyPI and download.pytorch.org. Installation instructions for the new release can be found at the familiar getting started p…

---

## [Heads-up: libtorch downloads now redirect to download-r2.pytorch.org by default — use curl -L](https://dev-discuss.pytorch.org/t/heads-up-libtorch-downloads-now-redirect-to-download-r2-pytorch-org-by-default-use-curl-l/3395)

<div class="topic-metadata">

**Author:** [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Replies:** 3\
**Last updated:** [July 7, 2026, 5:05pm UTC](https://dev-discuss.pytorch.org/t/heads-up-libtorch-downloads-now-redirect-to-download-r2-pytorch-org-by-default-use-curl-l/3395 "2026-07-07T17:05:03Z")

</div>

Starting next week (week of June 9, 2026), libtorch archive downloads from download.pytorch.org will be served from our R2-backed host, download-r2.pytorch.org, for faster and more reliable downloads. :warning: Importa…

---

## [PR stuck since a month](https://dev-discuss.pytorch.org/t/pr-stuck-since-a-month/3403)

<div class="topic-metadata">

**Author:** [@praful-srinivasan-02](https://dev-discuss.pytorch.org/u/praful-srinivasan-02)\
**Replies:** 2\
**Last updated:** [July 7, 2026, 8:25am UTC](https://dev-discuss.pytorch.org/t/pr-stuck-since-a-month/3403 "2026-07-07T08:25:07Z")

</div>

PR #184888 approved and green for a month, needs a land/merge.

[Next page](https://dev-discuss.pytorch.org/latest.md?page=1)
