pytorch / pytorch/vision

Patch versions of the wheel available in the CPU only pypi registry

Open
#9,253 3 comments 1 reaction 1 assignee View on GitHub

@scotts is already working on this.

Since Oct 30, 2025.

Dominant language
Python
Stars
17.9k
Forks
7.3k
Avg merge
1d 15h
Merged PRs (30d)
13

Description

In the CPU only pypi registry, https://download.pytorch.org/whl/torchvision/, I can see some dev/patch versions of the wheels:

torchvision-0.24.0+0429d73-cp311-cp311-win_arm64.whl
torchvision-0.24.0+0429d73-cp312-cp312-win_arm64.whl
torchvision-0.24.0+0429d73-cp313-cp313-win_arm64.whl
torchvision-0.24.0+7a9db90-cp311-cp311-win_arm64.whl
torchvision-0.24.0+7a9db90-cp312-cp312-win_arm64.whl
torchvision-0.24.0+7a9db90-cp313-cp313-win_arm64.whl
torchvision-0.24.0+b919bd0-cp311-cp311-win_arm64.whl
torchvision-0.24.0+b919bd0-cp312-cp312-win_arm64.whl
torchvision-0.24.0+b919bd0-cp313-cp313-win_arm64.whl
torchvision-0.24.0+e437e35-cp311-cp311-win_arm64.whl
torchvision-0.24.0+e437e35-cp312-cp312-win_arm64.whl
torchvision-0.24.0+e437e35-cp313-cp313-win_arm64.whl

I don't think they should be here in the wild, and it causes some confusion with uv where it's trying to use these, but is unable to download them.

Is there a valid reason for these wheels to be here? If not could they be removed?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.