On Sat, Jul 9, 2011 at 9:08 AM, Cal Leeming [Simplicity Media Ltd] < cal.leem...@simplicitymedialtd.co.uk> wrote:
> Python tracebacks can sometimes be cryptic, and difficult to understand. > And we've all had our fair share of times when we've seen a traceback and > thought "wtf?". > > This not one of them. > > In fact, in this rare example, the traceback is not only telling you what > is wrong, but it is also telling you how to fix the problem. > Unless it's wrong, which it might be, see: http://groups.google.com/group/django-users/msg/8a0302a09fbd7925. The code here is guessing about the reason for the problem, and offering the most likely solution. Possibly the original poster is confused by the exception message because in fact the solution proposed is already in place (though it would certainly help everyone who tries to help out if that were stated explicitly in the original question). Also see: https://code.djangoproject.com/ticket/15671. This is a ticket that was opened because this message can be wrong. It's recently been closed as fixed by a change in the way the request user attribute is implemented. I'm not 100% sure the change will fix the case where I saw this message incorrectly (haven't had a chance to check), but in newer code levels this check should be hiding fewer "other errors". Karen -- http://tracey.org/kmt/ -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
