#6918: Cannot set encoding of mail headers, only of message body
-----------------------------------------------------------+----------------
Reporter: Grzegorz Lukasik <[email protected]> | Owner:
serialx
Status: reopened | Milestone:
Component: django.core.mail | Version:
SVN
Resolution: | Keywords:
encoding mail headers
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------------------+----------------
Changes (by kmtracey):
* status: closed => reopened
* resolution: fixed =>
Comment:
Test is causing a failure on the buildbots:
http://buildbot.djangoproject.com/waterfall
Near as I can tell the only significant difference in the output is that
the test is expecting the multipart message to start:
{{{
Content-Type: multipart/alternative; boundary=
}}}
But instead is getting:
{{{
Content-Type: multipart/alternative;\n\tboundary=
}}}
Buildbots are ubutntu, running Pythons 2.4, 2.5, 2.6. Oddly enough the
test worked on my Ubuntu (older) using Python 2.5. Any clue what's
causing this? I suppose we can just change the test to not care whether
`multipart-alternative;` is followed by `\n\t` or not, since what we are
really testing for is that the correct encoding has been used in the
content....
--
Ticket URL: <http://code.djangoproject.com/ticket/6918#comment:7>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
