-
Notifications
You must be signed in to change notification settings - Fork 7.1k
properly deprecate legacy implementation #5387
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.
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
Conversation
💊 CI failures summary and remediationsAs of commit 2158a2c (more details on the Dr. CI page): ✅ None of the CI failures appear to be your fault 💚
🚧 1 ongoing upstream failure:These were probably caused by upstream breakages that are not fixed yet.
This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @pmeier , minor comment but LGTM when addressed and green
Thanks a ton @pmeier ! |
Hey @NicolasHug! 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 |
…0.14 (#5387) Summary: * properly deprecate legacy implementation * cleanup * use warning over deprecation directive * remove patch version * fix link in Kinetics docstring * Some more * fix affine functional tests Reviewed By: NicolasHug Differential Revision: D34140244 fbshipit-source-id: 889cb68f2b20fa8649a0922aa5085bcfd8da5027 Co-authored-by: Nicolas Hug <[email protected]>
Follow-up to #5386.