test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Removed some duplication. I suck at documentation. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@5551 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2007-06-27 12:43:28 +00:00
parent 987f8aa257
commit d605611bc5
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/email.txt
View File

@ -207,9 +207,6 @@ e-mail, you can subclass these two classes to suit your needs.
move to a more object-oriented design for e-mail messages and retain the move to a more object-oriented design for e-mail messages and retain the
original functions only for backwards compatibility. original functions only for backwards compatibility.
If you need to add new functionality to the e-mail infrastrcture,
sub-classing the ``EmailMessage`` class should make this a simple task.
In general, ``EmailMessage`` is responsible for creating the e-mail message In general, ``EmailMessage`` is responsible for creating the e-mail message
itself. ``SMTPConnection`` is responsible for the network connection side of itself. ``SMTPConnection`` is responsible for the network connection side of
the operation. This means you can reuse the same connection (an the operation. This means you can reuse the same connection (an