Hello everyone (and Malcolm especially)! This is about template rendering in unicode branch. Template's render now returns a byte string encoded in a DEFAULT_CHARSET. However just yesterday I've come across a case where a developer needed to render a template not to send it over HTTP connection but for some internal usage. It was then concatenated to some other unicode strings and failed with UnicodeDecodeError doing implicit unicode(). Then it striked me that we encode rendered output just for sending it over a wire and it should be handled in HttpResponse and send_email. In fact HttpResponse already encodes unicode objects using DEFAULT_CHARSET. Not sure about email machinery.
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
