Update on TorchVision’s future focus
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17.9k
- Forks
- 7.3k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 13
Description
Dear contributors and users,
I wanted to share an update on what we’ll be prioritizing in TorchVision from now on. In short:
In details:
- The
transforms.v2module, and pre-processing in general, remains our principal area of investments. We’ll keep investing in performance improvements and in new features. - The
utilsandopsmodules are maintained, but new features will only be added on a best-effort basis. - The
datasetsandmodelsmodules 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
iomodule 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This issue is a project-direction announcement covering transforms.v2, utils, ops, datasets, models, and io, but it names no implementation files or tests. Read the announcement and the linked TorchCodec project for context; no concrete change or completion condition is defined here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- computer-vision, machine-learning
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100