On 15 jun, 07:36, Russell Keith-Magee <[email protected]> wrote: > In this case, the underlying problem is that ImportError is actually > catching 2 different errors: > 1) The view specified doesn't exist > 2) The module containing the view contains an error.
Agreed, in this case this information is lost in get_callable, where the code does know the difference between 1) and 2), but the exception raised does not convey that. It might be a better idea to move the ViewDoesNotExist into the get_callable function, which get triggered with an AttributeException or an ImportError when the owning module can be imported. All other conditions are not caught. Bas -- 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.
