summaryrefslogtreecommitdiffstats
path: root/Doc/lib/email.tex
Commit message (Collapse)AuthorAgeFilesLines
* Delete the LaTeX doc tree.Georg Brandl2007-08-151-402/+0
|
* Typo fixAndrew M. Kuchling2007-07-141-1/+1
|
* Some new year updates.Georg Brandl2007-04-241-1/+1
|
* Some semantic fixes.Georg Brandl2007-04-011-1/+1
|
* More RFC 2231 improvements for the email 4.0 package. As Mark Sapiro rightlyBarry Warsaw2006-07-211-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | points out there are really two types of continued headers defined in this RFC (i.e. "encoded" parameters with the form "name*0*=" and unencoded parameters with the form "name*0="), but we were were handling them both the same way and that isn't correct. This patch should be much more RFC compliant in that only encoded params are %-decoded and the charset/language information is only extract if there are any encoded params in the segments. If there are no encoded params then the RFC says that there will be no charset/language parts. Note however that this will change the return value for Message.get_param() in some cases. For example, whereas before if you had all unencoded param continuations you would have still gotten a 3-tuple back from this method (with charset and language == None), you will now get just a string. I don't believe this is a backward incompatible change though because the documentation for this method already indicates that either return value is possible and that you must do an isinstance(val, tuple) check to discriminate between the two. (Yeah that API kind of sucks but we can't change /that/ without breaking code.) Test cases, some documentation updates, and a NEWS item accompany this patch.
* Merge email package 4.0 from the sandbox, including documentation, test cases,Barry Warsaw2006-03-181-21/+51
| | | | and NEWS updates.
* Bug #1210001: typo in email docGeorg Brandl2005-06-041-1/+1
|
* Big email 3.0 API changes, with updated unit tests and documentation.Barry Warsaw2004-10-031-10/+37
| | | | | | | | | | | | | | | | | Briefly (from the NEWS file): - Updates for the email package: + All deprecated APIs that in email 2.x issued warnings have been removed: _encoder argument to the MIMEText constructor, Message.add_payload(), Utils.dump_address_pair(), Utils.decode(), Utils.encode() + New deprecations: Generator.__call__(), Message.get_type(), Message.get_main_type(), Message.get_subtype(), the 'strict' argument to the Parser constructor. These will be removed in email 3.1. + Support for Python earlier than 2.3 has been removed (see PEP 291). + All defect classes have been renamed to end in 'Defect'. + Some FeedParser fixes; also a MultipartInvariantViolationDefect will be added to messages that claim to be multipart but really aren't. + Updates to documentation.
* Move a footnote to the end of the sentence, so the note mark won'tFred Drake2003-01-291-3/+4
| | | | interfere with the flow of the sentence.
* nitsBarry Warsaw2002-10-011-0/+31
|
* Split the long email package examples into separate files and useFred Drake2002-10-011-273/+4
| | | | | | \verbatiminput instead of the verbatim environment -- this does the "right thing" regarding page breaks in long examples for the typeset formats, and has nice benefits for the HTML version as well.
* Cleaned up the examples.Barry Warsaw2002-10-011-27/+22
|
* Proofread and spell checked, all except the Examples section (whichBarry Warsaw2002-10-011-18/+22
| | | | I'll do next).
* Vast update to email version 2. This could surely use proofreading.Barry Warsaw2002-10-011-136/+81
|
* Fix bug #573916. Sender and recipients reversed in email example.Raymond Hettinger2002-06-261-2/+2
|
* The "%" character does not need to be escaped in verbatim environments.Fred Drake2002-02-151-3/+3
| | | | This closes SF bug #517811.
* Add a clarification that the email package always deals in native lineBarry Warsaw2001-11-161-1/+13
| | | | | endings, and that it is smtplib's job to convert those to RFC 2821 line endings when sending the message.
* Finally fleshed out the examples section with 4 code samples! Some ofBarry Warsaw2001-11-051-1/+297
| | | | my own doing, some originally written by Matthew Dixon Cowles.
* Minor grammar and typo fixesAndrew M. Kuchling2001-11-051-2/+2
|
* Fix minor cut-and-paste typo.Barry Warsaw2001-10-091-1/+1
|
* Add documentation for the MIMEAudio class/module, contributed byBarry Warsaw2001-10-091-0/+26
| | | | Anthony Baxter.
* Markup adjustments.Fred Drake2001-09-271-4/+5
|
* Updates do email package documentation for markup, style, andBarry Warsaw2001-09-261-92/+28
| | | | organization.
* Start making some markup adjustments; Barry has indicated he will work onFred Drake2001-09-261-17/+17
| | | | this before we finish the integration, along with some restructuring.
* The email package documentation, currently organized the way I thinkBarry Warsaw2001-09-261-0/+358
Fred prefers. I'm not sure I like this organization, so it may change.