#27333: Different behavior py2 / py3 with Django on base64 body_encoding
EmailMessage
-------------------------------+----------------------------------------
Reporter: aRkadeFR | Owner: Claude Paroz
Type: Bug | Status: assigned
Component: Core (Mail) | Version: master
Severity: Normal | Resolution:
Keywords: email, base64 | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+----------------------------------------
Changes (by Claude Paroz):
* status: new => assigned
* needs_better_patch: => 0
* needs_tests: => 0
* version: 1.8 => master
* owner: nobody => Claude Paroz
* needs_docs: => 0
* stage: Unreviewed => Accepted
Comment:
Looks like a legitimate bug (I reproduced on master). The charset dance
we're doing in `SafeMIMEText.__init__` isn't sufficient for all cases,
apparently.
--
Ticket URL: <https://code.djangoproject.com/ticket/27333#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.c9561b379c7f548ee76788e52ce5382e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
