While I'm all in favor of faster template variable resolution, I've been poking at the new Variable class and noticed that the patch was apparently never updated for a post-Unicode Django; in some fairly simple tests I've been able to break it pretty badly by passing in Unicode strings and watching it blow up when it tries to output them.
I have a feeling this could cause headaches where authors of custom tags would need to be scrupulously careful about what they put into a Variable and how they read back out of it, so it'd be nice to move that care into the Variable class itself. Only problem is that I'm not really sure how :( Any suggestions? -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
