-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
Track ongoing deprecation #3372
Comments
+1 |
Do you think it's worth having a wrapper function that takes a version and a message...
or such. Inside we could check against the current version. Raise the appropriate warning. Assert If we used this everywhere we'd never miss any deprecations. We could also search for it to find all instances. |
@carltongibson Really interesting. |
Neat idea yeah. |
OK. I'll draft something up. (Put this in |
Closing as per #3404. Don't see this as a priority, hasn't been a problem. |
While we have a deprecation policy, we don't track the ongoing deprecations.
We need to have something similar to https://docs.djangoproject.com/en/1.8/internals/deprecation/ to help us conform to the policy.
The text was updated successfully, but these errors were encountered: