On 07/14/2010 02:28 PM, Russell Keith-Magee wrote:
I'm glad we've worked out that Weave is the culprit, but nobody has
answered the question of whether this is an indicator of a problem
with Django itself. What is weave passing as a header (and under what
conditions) that is causing a problem? Is there a need to improve
Django's error handling to protect against this case?
Yours,
Russ Magee %-)
Hi Russ.
I hate to admit that I didn't saved that offending value so someone can
reproduce this.
My reasoning back then for not raising a bug on django was this:
1. It was an obvious invalid value. As I said, Weave probably introduced
it at some point (I guess while still in beta) but other than that, it
could also be a number of things. Fixing that locale value solves it for
good. So I rinsed, wiped, forgot.
2. I tried to access some other django-powered sites with l10n, and they
loaded just fine. Only djangoproject.com and djangobook.com had the
problem. So my guess was that it was caused by something else on that
sites' stack and not django itself.
3. Improving the error-handling of django just didn't cross my mind.
I hope someone else with the same problem here could provide you with
the offending value.
Nick
--
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.
