ImportErrors are swallowed about django-modeltranslation HOT 2 CLOSED

From eschler on March 05, 2010 18:05:46
The whole thing behaves differently depending how you import modeltranslation. The
development server will raise the ImportError in models.py if modeltranslation is
directly in PYTHONPATH and imported like this:

{{{
from modeltranslation.translator import translator, TranslationOptions
}}}

The error will NOT be raised if imported from a sub module:

{{{
from project.modeltranslation import translator, TranslationOptions
}}}

The direct import doesn't solve the problem of swallowing, it is required to use a
workaround which raises the original error message. To do so, try to import a class
from your project's translation.py like this in a shell:

from project.translation import MyTranslationOptions

from django-modeltranslation.

From eschler on March 06, 2010 01:41:09
Workaround added in r32. Traceback is now printed explicitly.

from django-modeltranslation.