On Tue, Dec 1, 2009 at 7:56 PM, notcourage <klr...@gmail.com> wrote: > Is there a way to force django to show the full traceback? It only > shows the following though the query is called from the view home(req) > in my views.py: > > Traceback: > File "C:\swe\Python25\lib\site-packages\django\core\handlers\base.py" > in get_response > 92. response = callback(request, *callback_args, > **callback_kwargs) > File "c:\swe\python25\lib\site-packages\django\db\models\fields > \related.py" in __get__ > 191. rel_obj = self.related.model._base_manager.get > (**params) > File "c:\swe\python25\lib\site-packages\django\db\models\manager.py" > in get > 120. return self.get_query_set().get(*args, **kwargs) > File "c:\swe\python25\lib\site-packages\django\db\models\query.py" in > get > 305. % self.model._meta.object_name) > > Exception Type: DoesNotExist at / > Exception Value: Member matching query does not exist. >
Django isn't doing anything to the traceback here that would cause missing levels. What is the URL pattern that triggers this traceback? And the home view code? Karen -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
