check_for_language fails when django are imported from zip file

[jsantana@…]

If you import django from a zip file and some i18n utils fail (i.e django.views.i18n.javascript_catalog)

Steps:

1. import django as zip file
2. setup a javascript translation different from default with some strings, i.e locale/es/LC_MESSAGES/djangojs.{po,mo}
3. setup javascript_catalog view
4. make a request like ​http://server/i18n/?language=es

• expected result:

spanish catalog should be returned in javascript file

• result:

default language catalog is returned in javascript file

[Aymeric Augustin]

Django can't be packaged as a Python egg, in particular because it's hard to retrieve the templates and translation files.

If I understand correctly, by "importing from a zipfile", you mean "running from an egg", so it's a duplicate of #596.

[wiml@…]

Replying to aaugustin:

it's a duplicate of #596.

I think it is actually a duplicate of #8280.

The Django installation docs make reference to installing as an egg, there are various accepted patches for running from a zip file (eg #8238 and the aforementioned #8280), and apparently it is (was?) the preferred (only?) way to run Django on Google App Engine. - see ​https://developers.google.com/appengine/articles/django10_zipimport as well as other comments in those bugs.