#7722: EMail Message with CC - Carbon Copy
-------------------------------------------------------------+--------------
Reporter: roberto.digirolamo <[email protected]> | Owner:
nobody
Status: new | Milestone:
Component: django.core.mail | Version:
SVN
Resolution: | Keywords:
Stage: Design decision needed | Has_patch:
1
Needs_docs: 1 | Needs_tests:
1
Needs_better_patch: 0 |
-------------------------------------------------------------+--------------
Comment (by gert):
Call me old fashioned, but to me it seem silly to provide core email
functionality which handles HTML, attachments and even BCC but then tell
the developers that they have to subclass and make their own if they want
to CC.
Surely that does not sound like a framework for perfectionists with
deadlines?
I am willing to bet my lunch that anyone reading this at least once a day
writes or receives an email in which someone is CCed, this is basic
functionality (much more so than HTML or attachments) and need to be
implemented in the core.
PS: As previously suggested, add CC to the end of the parameter list if
backward compatibility needs to be maintained, but please add it.
--
Ticket URL: <http://code.djangoproject.com/ticket/7722#comment:12>
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.
