On Wed, 2008-08-20 at 11:46 -0700, Alfonso wrote: > Interestingly changing /django/core/handlers.py line 77 from: > > request.path_info) > > to: > > request.path) > > Makes everything work again - hmm. No idea why though.
So what you're saying is that if you introduce old bugs back into Django, your problem goes away? That's just hiding the symptom, not fixing the problem. Did you make all the necessary changes mentioned in the backwards incompatible changes page to accommodate that particular change in Django? See here for details: http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#ChangedthewayURLpathsaredetermined If you did make those changes, can you come up with a small example to demonstrate how the problem occurs. So far, you've just said that it occurs for a particular URL, but that isn't really enough to guess at the cause. For example, when the exception is raised, what is trying to unpack a sequence and what value is it trying to unpack (what is the thing that isn't a tuple, but is expected to be)? 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?hl=en -~----------~----~----~----~------~----~------~--~---
