Re: django error page: traceback too shallow?

I've definitely experienced missing levels in the traceback. I don't have anything reproducible, but notcourage isn't making it up. On Dec 8, 8:37 am, Karen Tracey wrote: > On Thu, Dec 3, 2009 at 1:24 AM, notcourage wrote: > > def home (request): > > >      

Re: django error page: traceback too shallow?

On Thu, Dec 3, 2009 at 1:24 AM, notcourage wrote: > def home (request): > >if (request.user.is_authenticated()): >artifacts = Artifact.objects.filter > (member__exact=request.user.profile.id) > ... >else: > ... > > In this case, the user is

Re: django error page: traceback too shallow?

def home (request): if (request.user.is_authenticated()): artifacts = Artifact.objects.filter (member__exact=request.user.profile.id) ... else: ... In this case, the user is authenticated but the predicate is failing as expected because user.profile is NULL. The

Re: django error page: traceback too shallow?

On Tue, Dec 1, 2009 at 7:56 PM, notcourage 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

django error page: traceback too shallow?

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 =