Remove deprecated APIs for 0.14
Closes https://github.com/pytorch/vision/issues/6257
git grep -n "0\.14" torchvision/ now gives zero output
@datumbox following up on https://github.com/pytorch/vision/pull/6258#discussion_r928926367 about the C++ models: if that works for you, I'll remove them in another PR. The only reason is that I fear that removing them might break some stuff internally. I'd rather isolate that in a separate PR, to avoid having to potentially revert other unrelated changes (like the rest of the deprecations).
@kazhang thanks for pointing out that _transforms_video.py is still referred internally so we need to discuss a plan for deprecating this particular file.
Thanks @jdsgomes . I opened D38393214 to see what tests might break if we removed these files.
@NicolasHug I don't have a super strong opinion about splitting the PRs if that simplifies your work. Curious why you think this can cause issues on FBcode though. As far as I see we don't even compile these sources on BUCK, so I don't see how people are using them. Have you saw anything different? If not, you can add the removal here; otherwise send a separate PR that removes the endpoints in question as you proposed.
Happy to provide the necessary stamps once you confirm things work on FBcode + the tests pass.
@NicolasHug @datumbox @jdsgomes Could you check if this PR is okay to merge? I think regarding the removal of deprecated API, other than this PR only the following two things left:
- Removal of cpp models: https://github.com/pytorch/vision/pull/6632
- To be discussed whether or not we remove
transforms/_functional_video.pyandtransforms/_transforms_video.pybut we agree this will be on separate PR
I have checked and everything seems fine to me on this PR and I prefer if we can merge this PR faster and do fbsync in case anything we need to revert.
@NicolasHug do you prefer to do this on a new PR so that the attribution is right?
Just FYI, the changes in this PR come from my commits.
But whether this PR gets merged or another makes no difference to me.
Just to update, I found 2 breakages internally after trying this changes. I have created diffs to fix for each of them, and I will merge this PR once the fix is landed.
The failed test seems to be not related to this PR, will merge
Hey @YosuaMichael!
You merged this PR, but no labels were added. The list of valid labels is available at https://github.com/pytorch/vision/blob/main/.github/process_commit.py