8000 Update on TorchVision’s future focus · Issue #9036 · pytorch/vision · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Update on TorchVision’s future focus #903 8000 6

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.

Sign up for GitHub

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

Jump to bottom
Open
NicolasHug opened this issue Apr 23, 2025 · 0 comments
Open

Update on TorchVision’s future focus #9036

NicolasHug opened this issue Apr 23, 2025 · 0 comments

Comments

@NicolasHug
Copy link
Member
NicolasHug commented Apr 23, 2025 •
edited
Loading

Dear contributors and users,

I wanted to share an update on what we’ll be prioritizing in TorchVision from now on. In short:

Image

In details:

  • The transforms.v2 module, and pre-processing in general, remains our principal area of investments. We’ll keep investing in performance improvements and in new features.
  • The utils and ops modules are maintained, but new features will only be added on a best-effort basis.
  • The datasets and models modules are still usable and they are not deprecated, but we’ll decrease support. This may mean for example that if a dataset URL breaks, we won’t necessarily actively try to fix the download functionality. The models are already very stable, so regressions are unlikely. New features will likely not be added.
  • The capabilities of the io module will eventually move to TorchCodec, where we’re consolidating all of PyTorch encoding/decoding capabilities:
    • For video, changes are effective from now (0.22): the video decoding and encoding capabilities are deprecated and will be removed in 0.24 (end of 2025)!. We strongly encourage you to migrate towards TorchCodec ASAP.
    • The image decoders/encoders remain in torchvision for the time being. They will eventually be migrated to TorchCodec, but there is no ETA on this for now. The migration will involve our usual 2-version deprecation cycle, so you’ll be given a heads-up.

Most of these changes are contributor-facing, not user-facing. As a result, contributors may observe reduced engagement on issues and PRs that relate to the de-prioritized areas (models, datasets, ops and utils).

EDIT: Deleted some comments below which were feature requests and unrelated questions. Feel free to comment on this issue with questions that are in scope, but please open separate issues for feature requests.
@NicolasHug NicolasHug pinned this issue Apr 23, 2025
@AntoineSimoulin AntoineSimoulin mentioned this issue May 22, 2025
Open
@pytorch pytorch deleted a comment from twsl Jun 10, 2025
@pytorch pytorch deleted a comment from gammag4 Jun 10, 2025
@pytorch pytorch deleted a comment from genji970 Jun 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@NicolasHug
0