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? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Contexts have been made context managers in django (https://docs.djangoproject.com/en/1.9/ref/templates/api/#django.template.Context.update), so widgy.utils.update_context is obviated. We should remove internal uses of it, and throw a deprecation warning when it's called from user code.
The text was updated successfully, but these errors were encountered:
yay!
-rocky
On Thu, Apr 28, 2016 at 7:09 AM, Gavin Wahl notifications@github.com wrote:
Contexts have been made context managers in django ( https://docs.djangoproject.com/en/1.9/ref/templates/api/#django.template.Context.update), so widgy.utils.update_context is obviated. We should remove internal uses of it, and throw a deprecation warning when it's called from user code. — You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub #373
Contexts have been made context managers in django ( https://docs.djangoproject.com/en/1.9/ref/templates/api/#django.template.Context.update), so widgy.utils.update_context is obviated. We should remove internal uses of it, and throw a deprecation warning when it's called from user code.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub #373
Sorry, something went wrong.
No branches or pull requests
Contexts have been made context managers in django (https://docs.djangoproject.com/en/1.9/ref/templates/api/#django.template.Context.update), so widgy.utils.update_context is obviated. We should remove internal uses of it, and throw a deprecation warning when it's called from user code.
The text was updated successfully, but these errors were encountered: