Python 3 displays the original exception alongside the new exception when a new exception occurs in an except block. The AttributeError is expected, so this doesn't tell you anything about what goes wrong. The second error occurs when importing `self.urlconf_name`. The traceback should point you to the exact cause of this second error, that's the error you will have to solve to resolve this issue.
On Monday, November 23, 2015 at 1:07:29 PM UTC+1, KwangYoun Jung wrote:
-- On Monday, November 23, 2015 at 1:07:29 PM UTC+1, KwangYoun Jung wrote:
Did you solve the issue?
On Tuesday, July 2, 2013 at 8:14:00 PM UTC+9, Pratik Mandrekar wrote:Hello,I keep getting the error AttributeError: 'RegexURLResolver' object has no attribute '_urlconf_module' and the only trace available is as shown below:'RegexURLResolver' object has no attribute '_urlconf_module'My Sentry Error reporting normally shows the above error along with another error, both of which seem to happen simultaneously
django.core.urlresolvers in urlconf_module
AttributeError: 'RegexURLResolver' object has no attribute '_urlconf_module'
The trace for which is
return self._urlconf_module
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5a1ab7e7-16cd-4c54-8ad1-ce3978813682%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment