-
Notifications
You must be signed in to change notification settings - Fork 402
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
Remove deprecated code for next v0.9 #956
Comments
|
|
I will work on |
Hey, I would like to work on compute_on_step in image, is that possible? |
Yes, definitely! Feel free to start! :] |
I would like to pick up retrieval as well! 😄 |
@tanmoyio how is it going with the change for audio? |
@tanmoyio sorry I was in vacation, I will do it today. |
Cool! 🎉 Thank you all! |
🚀 Feature
Let's start standard deprecated API cleaning and also split it into smaller contributions that are not affecting each other, and they are easier/faster to review... So each of the following ToDO shall be addressed in a single PR.
Before you start working on any, pls ping/comment us here so we can assign it to you to reduce work collision 🐰
Motivation
Regular API cleaning of deprecated API keeping the codebase in a healthy state
Pitch
Ideal hands-on / first contribution because of its low complexity 💜
Alternatives
compute_on_step
in aggregation -> Removecompute_on_step
from aggregation and tests #990compute_on_step
in audio -> Removed Deprecated compute_on_step from audio #1007compute_on_step
in classification -> Removed Deprecatedcompute_on_step
from Classification #962compute_on_step
in detection -> Removecompute_on_step
from detection #1005compute_on_step
in image -> remove deprecated compute_on_step from torchmetrics/image #979compute_on_step
in regression -> Remove deprecatedcompute_on_step
in Regression #967compute_on_step
in retrival -> remove compute_on_step in torchmetrics/retrieval #993compute_on_step
in text -> Removecompute_on_step
from text #1004compute_on_step
in wrappers -> Removecompute_on_step
from wrappers #991Additional context
The text was updated successfully, but these errors were encountered: