David Cramer wrote: > Is there any reason why its storing the keys in QueryDict (possibly > others) as unicode? >
i think it's for consistency. i mean, when i see mentioned that django is fully unicode, i assume every string i get from django is in unicode, unless there's a very good reason for the opposite. and in this case, it seems to me that unicode strings make sense. for example, what if the keys contain non-ascii data? > This seems like a bug, possibly overlooked, but having unicode keys > prevents certain functionality like **request.GET in a method call. hmmm.. well, you can always convert it, can't you? :) anyway... isn't simply sending in the GET params to functions a little dangerous? gabor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
