#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 Gary Wilson <[EMAIL PROTECTED]>):
Replying to [comment:27 anonymous]:
> It is not clear how the EmailMessage class will maintain backward
compatibility.
Well, it's not completely necessary to maintain backward compatibility, as
it's not guaranteed until 1.0.
> 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.
The patch for this ticket maintains backwards compatibility since it
allows for a variable length `datatuple`, but what happens when it's time
to add the features from other tickets? The interface would probably have
to be changed anyway. If the interface is fixed first (with
`EmailMessage` in #3366?), then all these features from the various
tickets could be added afterwards (separately or together) without
breaking anything.
--
Ticket URL: <http://code.djangoproject.com/ticket/1541#comment:28>
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
-~----------~----~----~----~------~----~------~--~---
