The Django docs indicate that the built-in translation middleware (which we don't use) prefers 'request.LANGUAGE_CODE'. For compatibility with 3rd party apps (and to make a waffle upgrade possible) we should switch. This if probably a big patch, but almost entirely search-and-replace, unless some lines need to be rewrapped.  https://docs.djangoproject.com/en/1.3/topics/i18n/deployment/#how-django-discovers-translations
To clarify, is this something we should fix sooner rather than later, or is this something we can stick in the code quality pile to be fixed in an upcoming house-keeping week?
Hello i would like to try this. Thanks
Let me know if you have any questions!
Can I pick it?
(In reply to Michał Frontczak :fxa90id from comment #4) > Can I pick it? go for it :)
Landed on master: https://github.com/mozilla/kitsune/commit/d3db15ec11cbb0ff26a2a179d83713c25229b97a
Deployed to prod.
Thanks Michał this was awesome!