- 30 Agu, 2007 1 kayıt (commit)
-
-
Guido van Rossum yazdı
-
- 25 Agu, 2007 1 kayıt (commit)
-
-
Guido van Rossum yazdı
Once Barry and the email-sig have a working new version we'll add it back. If it doesn't make the 3.0a deadline (release August 31), too bad.
-
- 09 Agu, 2007 1 kayıt (commit)
-
-
Guido van Rossum yazdı
Completely get rid of StringIO.py and cStringIO.c. I had to fix a few tests and modules beyond what Christian did, and invent a few conventions. E.g. in elementtree, I chose to write/return Unicode strings whe no encoding is given, but bytes when an explicit encoding is given. Also mimetools was made to always assume binary files.
-
- 21 Nis, 2006 1 kayıt (commit)
-
-
Thomas Wouters yazdı
number of tests, all because of the codecs/_multibytecodecs issue described here (it's not a Py3K issue, just something Py3K discovers): http://mail.python.org/pipermail/python-dev/2006-April/064051.html Hye-Shik Chang promised to look for a fix, so no need to fix it here. The tests that are expected to break are: test_codecencodings_cn test_codecencodings_hk test_codecencodings_jp test_codecencodings_kr test_codecencodings_tw test_codecs test_multibytecodec This merge fixes an actual test failure (test_weakref) in this branch, though, so I believe merging is the right thing to do anyway.
-
- 03 Eki, 2004 1 kayıt (commit)
-
-
Barry Warsaw yazdı
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.
-
- 09 May, 2004 1 kayıt (commit)
-
-
Barry Warsaw yazdı
This Parser is now just a backward compatible front-end to the FeedParser.
-
- 20 Mar, 2004 1 kayıt (commit)
-
-
Thomas Wouters yazdı
> ---------------------------- > revision 1.20.4.4 > date: 2003/06/12 09:14:17; author: anthonybaxter; state: Exp; lines: +13 -6 > preamble is None when missing, not ''. > Handle a couple of bogus formatted messages - now parses my main testsuite. > Handle message/external-body. > ---------------------------- > revision 1.20.4.3 > date: 2003/06/12 07:16:40; author: anthonybaxter; state: Exp; lines: +6 -4 > epilogue-processing is now the same as the old parser - the newline at the > end of the line with the --endboundary-- is included as part of the epilogue. > Note that any whitespace after the boundary is _not_ part of the epilogue. > ---------------------------- > revision 1.20.4.2 > date: 2003/06/12 06:39:09; author: anthonybaxter; state: Exp; lines: +6 -4 > message/delivery-status fixed. > HeaderParser fixed. > ---------------------------- > revision 1.20.4.1 > date: 2003/06/12 06:08:56; author: anthonybaxter; state: Exp; lines: +163 -129 > A work-in-progress snapshot of the new parser. A couple of known problems: > > - first (blank) line of MIME epilogues is being consumed > - message/delivery-status isn't quite right > > It still needs a lot of cleanup, but right now it parses a whole lot of > badness that the old parser failed on. I also need to think about adding > back the old 'strict' flag in some way. > =============================================================================
-
- 06 Mar, 2003 1 kayıt (commit)
-
-
Barry Warsaw yazdı
Rename a constant.
-
- 05 Kas, 2002 2 kayıt (commit)
-
-
Barry Warsaw yazdı
where in lax parsing, the first non-header line after a header block (e.g. the first line not containing a colon, and not a continuation), can be treated as the first body line, even without the RFC mandated blank line separator. rfc822 had this behavior, and I vaguely remember problems with this, but can't remember details. In any event, all the tests still pass, so I guess we'll find out. ;/ This patch works by returning the non-header, non-continuation line from _parseheader() and using that as the first header line prepended to fp.read() if given. It's usually None. We use this approach instead of trying to seek/tell the file-like object.
-
Barry Warsaw yazdı
multipart/digest isn't a message/rfc822. This is legal, but counter to recommended practice in RFC 2046, $5.1.5. The fix is to look at the content type after setting the default content type. If the maintype is then message or multipart, attach the parsed subobject, otherwise use set_payload() to set the data of the other object.
-
- 07 Eki, 2002 1 kayıt (commit)
-
-
Barry Warsaw yazdı
get_type(). Also, one of the regular expressions is constant so might as well make it a module global. And, when splitting up digests, handle lineseps that are longer than 1 character in length (e.g. \r\n).
-
- 30 Eyl, 2002 1 kayıt (commit)
-
-
Barry Warsaw yazdı
-
- 28 Eyl, 2002 1 kayıt (commit)
-
-
Barry Warsaw yazdı
-
- 10 Eyl, 2002 1 kayıt (commit)
-
-
Barry Warsaw yazdı
boundary could be found -- in a lax parser -- the entire body is assigned to the message payload.
-
- 23 Agu, 2002 1 kayıt (commit)
-
-
Tim Peters yazdı
-
- 19 Tem, 2002 1 kayıt (commit)
-
-
Barry Warsaw yazdı
non-strict parsing should be the default. Make it so.
-
- 18 Tem, 2002 1 kayıt (commit)
-
-
Barry Warsaw yazdı
quoting: in non-strict mode, messages don't require a blank line at the end with a missing end-terminator. A single newline is sufficient now. Handle trailing whitespace at the end of a boundary. Had to switch from using string.split() to re.split() Handle whitespace on the end of a parameter list for Content-type. Handle whitespace on the end of a plain content-type header. Specifically, get_type(): Strip the content type string. _get_params_preserve(): Strip the parameter names and values on both sides. _parsebody(): Lots of changes as described above, with some stylistic changes by Barry (who hopefully didn't screw things up ;).
-
- 09 Tem, 2002 1 kayıt (commit)
-
-
Barry Warsaw yazdı
argument to the constructor -- defaulting to true -- which is different than Anthony's approach of using global state. parse(), parsestr(): Grow a `headersonly' argument which stops parsing once the header block has been seen, i.e. it does /not/ parse or even read the body of the message. This is used for parsing message/rfc822 type messages. We need test cases for the non-strict parsing. Anthony will supply these. _parsebody(): We can get rid of the isdigest end-of-line kludges, although we still need to know if we're parsing a multipart/digest so we can set the default type accordingly.
-
- 02 Haz, 2002 1 kayıt (commit)
-
-
Barry Warsaw yazdı
parent is now a multipart with one element, the sub-message object).
-
- 19 May, 2002 1 kayıt (commit)
-
-
Barry Warsaw yazdı
email package's Parser to handle the three common line endings. Certain protocols such as IMAP define CRLF line endings and it doesn't make sense for the client app to have to normalize the line endings before handing it message off to the Parser. _parsebody(): Be more flexible in the matching of line endings for finding the MIME separators. Accept any of \r, \n and \r\n. Note that we do /not/ change the line endings in the payloads, we just accept any of those three around MIME boundaries.
-
- 10 Nis, 2002 1 kayıt (commit)
-
-
Barry Warsaw yazdı
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 ;).
-
- 27 Ock, 2002 1 kayıt (commit)
-
-
Barry Warsaw yazdı
that the first subpart added makes the payload a list object. Otherwise, a multipart/* with only one subpart will not have the proper structure.
-
- 11 Eki, 2001 1 kayıt (commit)
-
-
Barry Warsaw yazdı
headers. It does not parse the body of the message, instead simply assigning it as a string to the container's payload. This can be much faster when you're only interested in a message's header.
-
- 04 Eki, 2001 2 kayıt (commit)
-
-
Barry Warsaw yazdı
-
Tim Peters yazdı
-
- 26 Eyl, 2001 1 kayıt (commit)
-
-
Barry Warsaw yazdı
Also, add a clause to the big-if to handle message/delivery-status content types. These create a message with subparts that are Message instances, which best represent the header blocks of this content type.
-
- 23 Eyl, 2001 1 kayıt (commit)
-
-
Barry Warsaw yazdı
<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).
-