-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Deprecate merged extensions #1203
Comments
I think it may be better to add the deprecation warning in a new minor 2.x release and remove them in 3.0 |
This warning would be for the extensions, that function is part of the built-in support that superseded the extensions. The extensions are in |
Only those two extensions are deprecated, not all extensions, so you shouldn't add the deprecation to the base class. |
that makes sense to me. Is it okay to begin working on this? |
Sure! |
autoescape
andwith
have been in the standard compiler for years now. The extensions do nothing. Make them issue a deprecation warning, for removal in 3.1.The text was updated successfully, but these errors were encountered: