#1541: [patch] Add multipart message capability to django.core.mail
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: jacob
Status: assigned | Component: django.core.mail
Version: | Resolution:
Keywords: | Stage: Design decision
needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------------------+----------------------------------------
Comment (by anonymous):
Replying to [comment:25 [EMAIL PROTECTED]:
> How does that sound?
Sounds good. I have a few concerns/comments. I prefer an approach where I
do not have to know what SafeMIMEMultipart is. It is not clear how the
EmailMessage class will maintain backward compatibility. We will be
spending a lot of time accepting an interface and implementation for
EmailMessage, and have to disturb everyone when that patch is applied. Not
many people are interested, this is not newforms ;) I'd recommend applying
patch 3 now and after that, working on #3366.
--
Ticket URL: <http://code.djangoproject.com/ticket/1541#comment:27>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
