On 24 févr. 2014, at 21:52, anubhav joshi <[email protected]> wrote:
> 2.) There it says: "Import errors discovered during application loading > during can be masked under certain circumstances." > If I could get a better explanation of this, it would be very helpful. > > Also If I could get an answer to the above. Overall, this happens when Django catches an exception and re-raises another exception, usually ImproperlyConfigured, in order to provide a "more helpful" error message. This gets nasty when the original exception is already hard to diagnose with the full context, for instance when it's an ImportError triggered by a circular import. It's also quite bad when another part of Django catches ImproperlyConfigured again. I've seen that, but I cannot remember where. There's a particularly vicious variant of the circular import problem: when it's triggered by a reentrant call to the app cache population process. Attempts to remove the faulty circular import may change the import sequence and create another circular imports, making for a particularly annoying whack-a-mole game. This is fixed in 1.7. Have a look at my posts discussing circular imports in the context of app-loading in December and early January for details. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/C75A99A3-FD6B-449C-92E1-AB0342E43416%40polytechnique.org. For more options, visit https://groups.google.com/groups/opt_out.
