On Fri, 2006-06-16 at 01:36 +0000, jacob wrote:
> Actually, I think it is coming from a different spot. Here's the full
> method:
>
> 24 def get_user_id(request):
> 25 user_id = request.session.get('user_id')
> 26 if user_id:
> 27 return request.session['user_id']
And you did this because "return user_id" was too easy? :-)
> 28 else:
> 29 return HttpResponseRedirect('/login/')
>
> If I raise my own exception between 28 & 29 I get the exception instead
> of the one shown above. Is this happening in HttpResponseRedirect()?
>
> /login/ renders fine if I request it directly in a browser.
I don't think you've narrowed it down far enough still. From the
original traceback you posted, the final jumping-off point from your
code into Django's internals was
File "/home/misjxm/dp1/file/app/views.py" in inbox
42. for r in rcpt_list:
So I would be looking at the view function you are redirecting to and
going over that with the fine-toothed bug detector.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
