Basically the plumbing under EmailMessage needs to know about its encoding, for some reason the only place where encoding is defaulted to DEFAULT_CHARSET is message. I moved it to class init.
Fixed EmailMessage default encoding.
@dmishe Can you please open a ticket and add tests?
This is from py3 sprint times, I am not even sure it's still relevant, I'll check
This could be a good idea, but I don't understand what you're trying to achieve exactly: making EmailMessage more easily customizable via subclassing?
At the time of py3 sprint, this was a breaking bug, because IIRC EmailMessage didn't know about it's encoding and tried to use ascii, because encoding wasn't passed down to it
Is there a trac ticket?
No, it's old and was a part of py3 sprint, I don't think it's relevant anymore.