Re: django error page: traceback too shallow?

2009-12-09 Thread Larrik Jaerico
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):
>
> >        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 traceback is just odd.
>
> I have not seen anything like missing levels in a traceback, nor can I
> recreate anything like what you are reporting based on the information
> provided.  If you can post a complete small example (models, url patterns,
> view) that demonstrates what you see, someone might be able to help more.
>
> 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.




Re: django error page: traceback too shallow?

2009-12-08 Thread Karen Tracey
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 authenticated but the predicate is failing
> as expected because user.profile is NULL. The traceback is just odd.
>
>
I have not seen anything like missing levels in a traceback, nor can I
recreate anything like what you are reporting based on the information
provided.  If you can post a complete small example (models, url patterns,
view) that demonstrates what you see, someone might be able to help more.

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.




Re: django error page: traceback too shallow?

2009-12-02 Thread notcourage
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 traceback is just odd.

--

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.




Re: django error page: traceback too shallow?

2009-12-01 Thread Karen Tracey
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 "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.