As lukeplant commented on a ticket: This is proposing the same thing as #12794<http://code.djangoproject.com/ticket/12794>, but for a different reason.
#13217 <http://code.djangoproject.com/ticket/13217> is related, but the solution proposed here was not proposed there, and doesn't have the same issues that caused the WONTFIX on that ticket. This change would help that problem if the cache is able to cache by language cookie. I'm not in favour of yet another setting if we can avoid it - we need to know if there are any downsides to always storing in the cookie rather than the session. If not, we always store in the cookie. Since we've documented the current behaviour, we may however need a deprecation path involving a setting. So it's now about whether to be backwards compatible but add another setting and complicate things a bit, or not to be backwards compatible and move current language to separate cookie permanently. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
