summaryrefslogtreecommitdiffstats
path: root/Lib/email/__init__.py
Commit message (Collapse)AuthorAgeFilesLines
* whitespace n11nAnthony Baxter2006-03-201-8/+8
|
* Merge email package 4.0 from the sandbox, including documentation, test cases,Barry Warsaw2006-03-181-3/+74
| | | | and NEWS updates.
* Ported 42075 from release23-maint branch.Barry Warsaw2006-01-171-2/+2
| | | | | | | | | | | SF bug #1403349 solution for email 3.0; some MUAs use the 'file' parameter name in the Content-Distribution header, so Message.get_filename() should fall back to using that. Will port to the Python 2.5 trunk. Also, bump the email package version to 3.0.1 for eventual release. Of course, add a test case too. XXX Need to update the documentation.
* Fixes for SF #1076485, which I'll apply to the CVS head too. The problem wasBarry Warsaw2004-12-051-1/+1
| | | | | | | | | | | | | | | | caused by a self._input.readline() call that wasn't checking for the NeedsMoreData marker. msg_43.txt contains a message that illustrates the problem, when email.message_from_*() is called. That interface uses the Parser API, which splits reads into 8192 byte chunks. It so happens that for the test message, the 8192 chunk falls inside a message/delivery-status, which is where in the FeedParser the readline() call was that didn't check for NeedsMoreData. I also added an assert to unreadline() so it'll be more evident if an attempt to push back NeedsMoreData ever happens again. Bump the email package version number.
* There's likely nothing more to do to the email package before Python 2.4 isBarry Warsaw2004-11-291-1/+1
| | | | final, so I'm marking email's version number as "3.0" (e.g. final).
* All known bugs are closed, and Python 2.4b1 is coming out soon, so bumpBarry Warsaw2004-10-091-1/+1
| | | | email's version number to 3.0b1.
* Big email 3.0 API changes, with updated unit tests and documentation.Barry Warsaw2004-10-031-11/+6
| | | | | | | | | | | | | | | | | 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.
* Update to Python 2.3, getting rid of backward compatiblity crud.Barry Warsaw2004-05-091-20/+5
|
* Bump version number to 2.5.5Barry Warsaw2003-12-301-1/+1
|
* Bump the version number for the standalone mimelib package.Barry Warsaw2003-08-191-1/+1
|
* _make_boundary(): Fix for SF bug #745478, broken boundary calculationBarry Warsaw2003-05-291-1/+1
| | | | | | | | | in some locales. This code simplifies the boundary algorithm to use randint() which is what we wanted anyway. Bump package version to 2.5.3. Backport candidate for Python 2.2.3
* Bump version numberBarry Warsaw2003-05-081-1/+1
|
* Bump to version 2.5.1Barry Warsaw2003-03-301-1/+1
|
* Temporary bump of the version number.Barry Warsaw2003-03-261-1/+1
|
* Email version 2.5 -- I will now backport this to Python 2.2.3.Barry Warsaw2003-03-211-1/+1
|
* beta 1Barry Warsaw2003-03-111-1/+1
|
* Actually, make this 2.5a1 since it will include API changes that mayBarry Warsaw2002-12-301-1/+1
| | | | need more vetting, and it will be included in Python 2.3a1.
* Bump to 2.5Barry Warsaw2002-12-301-1/+1
|
* Bump __version__ (yes, to 2.5 "minus")Barry Warsaw2002-11-051-1/+1
|
* Bump the __version__Barry Warsaw2002-10-141-1/+1
|
* Bump version number to 2.4.2 to pick up the latest minor bug fixes.Barry Warsaw2002-10-101-1/+1
|
* Bump the version to 2.4.1 (not 2.5 as previously mentioned) to sync itBarry Warsaw2002-10-071-1/+1
| | | | with the standalone mimelib package.
* __all__: UpdatedBarry Warsaw2002-09-301-20/+22
|
* The ansi_x3.4_1968 encoding is an alias for ascii, but isn't known inBarry Warsaw2002-09-301-0/+9
| | | | | | | | Python 2.1.3. However it's required by the email tests suite, so poke it into the encodings aliases if it's missing. The is apparently the approved API for doing so. Now we can remove the hexversion shortcircuits in the test suite.
* Code cleanup and add docstrings.Barry Warsaw2002-09-281-2/+17
|
* __version__: Bump to 2.4Barry Warsaw2002-09-251-9/+16
| | | | | | | | | | | Move the imports of Parser and Message inside the message_from_string() and message_from_file() functions. This way just "import email" won't suck in most of the submodules of the package. Note: this will break code that relied on "import email" giving you a bunch of the submodules, but that was never documented and should not have been relied on.
* Bump to 2.3.1 to pick up the missing file.Barry Warsaw2002-09-121-1/+1
|
* Bump version number to 2.3Barry Warsaw2002-08-201-1/+1
|
* message_from_string(), message_from_file(): The consensus on theBarry Warsaw2002-07-191-2/+2
| | | | | mimelib-devel list is that non-strict parsing should be the default. Make it so.
* Anthony Baxter's patch to expose the parser's `strict' flag in theseBarry Warsaw2002-07-181-5/+5
| | | | convenience functions. Closes SF # 583188 (python project).
* With the addition of Oleg's support for RFC 2231, it's time to bumpBarry Warsaw2002-07-091-1/+1
| | | | the version number to 2.1.
* Bump to version 2.0.5, and also use absolute import paths.Barry Warsaw2002-06-011-3/+3
|
* Bump to version 2.0.4Barry Warsaw2002-05-221-1/+1
|
* Complete a merge of the mimelib project and the Python cvs codebasesBarry Warsaw2002-05-191-1/+1
| | | | | | | | | | | | | for the email package. The former is now just a shell project that has some extra files for packaging for independent use (e.g. setup.py and README). Added a compatibility layer so that the same API can be used in Python 2.1 and 2.2/2.3 with the major differences shuffled off into helper modules (_compat21.py and _compat22.py). Also bumped the package version number to 2.0.3 for some fixes to be checked in momentarily.
* Sync'ing with standalone email package 2.0.1. This adds support forBarry Warsaw2002-04-101-3/+7
| | | | | | | | | non-us-ascii character sets in headers and bodies. Some API changes (with DeprecationWarnings for the old APIs). Better RFC-compliant implementations of base64 and quoted-printable. Updated test cases. Documentation updates to follow (after I finish writing them ;).
* Fix __all__ to the current list of exported modules (must pass theBarry Warsaw2001-10-091-3/+4
| | | | tests in test_email.py).
* Give me back my page breaks.Barry Warsaw2001-10-041-1/+1
|
* Whitespace normalization.Tim Peters2001-10-041-1/+1
|
* The email package version 1.0, prototyped as mimelibBarry Warsaw2001-09-231-0/+34
<http://sf.net/projects/mimelib>. There /are/ API differences between mimelib and email, but most of the implementations are shared (except where cool Py2.2 stuff like generators are used).
generated by cgit v0.12 at 2024-10-23 06:32:34 (GMT)