Hello, Based on the discussion I had on #django-sprint with Alex_Gaynor and jezdez it seems that this ticket #5691[1] needs a design decision before being committed because it changes the cache key for i18n site.
What is the issue ? As of now the pages are save under the same key in cache without any distinction of their language "fr", "en", "es" * cache_key = _generate_cache_header_key(key_prefix, request) The consequence of this behavior is that django's cached pages are broken on i18n site ; dajngo ends up serving a page from the cache without taking care of the language requested by the user this leads django to serve the page from the cache indifferently of the language requested by the user. The proposed solution append the language to the key if the site use "USE_I18N" = True : * cache_key += ".%s" % translation.get_language() I hope that the fact that this bug make django's cache useless for i18n site and the fact that this key was undocumented will make the integration of the proposed patch possible. I would be glad to hear from about this issue ? Regards, --yml [1] http://code.djangoproject.com/ticket/5691 -- 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.
