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.
That sounds reasonable.
Malcolm
Just was about to make a patch but saw your changeset implementing it.
Thanks!