We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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?
to your account
autoescape and with 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:
I think it may be better to add the deprecation warning in a new minor 2.x release and remove them in 3.0
Sorry, something went wrong.
@davidism for clarification, would this warning be printed when this (
This warning would be for the extensions, that function is part of the built-in support that superseded the extensions.
The extensions are in ext.py, you'd want to override the __init__ method for WithExtension, and AutoEscapeExtension to show a deprecation warning.
@davidism Because those two classes take in this init method here:
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?
Successfully merging a pull request may close this issue.