- 10 Eyl, 2016 1 kayıt (commit)
-
-
R David Murray yazdı
It turns out we can't depend on email.message getting imported every place message_factory is needed, so to avoid a circular import we need to special case Policy.message_factory=None in the parser instead of using monkey patching. I had a feeling that was a bad idea when I did it.
-
- 09 Eyl, 2016 1 kayıt (commit)
-
-
R David Murray yazdı
-
- 07 Eyl, 2016 1 kayıt (commit)
-
-
R David Murray yazdı
Original patch by Martin Panter, new policy fixes by me.
-
- 08 Eyl, 2016 1 kayıt (commit)
-
-
R David Murray yazdı
And most of the tools. Patch by Emanual Barry, reviewed by me, Serhiy Storchaka, and Martin Panter.
-
- 16 Tem, 2016 1 kayıt (commit)
-
-
R David Murray yazdı
Patch by Costas.
-
- 23 May, 2015 1 kayıt (commit)
-
-
Raymond Hettinger yazdı
-
- 26 Ock, 2015 1 kayıt (commit)
-
-
Benjamin Peterson yazdı
Patch by Cory Benfield.
-
- 12 Agu, 2014 1 kayıt (commit)
-
-
Serhiy Storchaka yazdı
Original patch by Raymond Hettinger.
-
- 07 Şub, 2014 1 kayıt (commit)
-
-
R David Murray yazdı
In 3.5 I will fix this right by adding a message_factory attribute to the policy.
-
- 14 Şub, 2013 1 kayıt (commit)
-
-
R David Murray yazdı
Original patch submitted by QNX, modified for clarity by me (mostly comments). QNX reports a 30% speed up in average email parsing time.
-
- 18 Ara, 2012 2 kayıt (commit)
-
-
Andrew Svetlov yazdı
Patch by Serhiy Storchaka.
-
Andrew Svetlov yazdı
Patch by Serhiy Storchaka.
-
- 28 May, 2012 2 kayıt (commit)
-
-
R David Murray yazdı
This commit also restores the news item for 167256 that it looks like Terry inadvertently deleted. (Either that, or I don't understand now merging works...which is equally possible.)
-
R David Murray yazdı
This patch also deprecates the MalformedHeaderDefect. My best guess is that this defect was rendered obsolete by a refactoring of the parser, and the corresponding defect for the new parser (which this patch introduces) was overlooked.
-
- 25 May, 2012 1 kayıt (commit)
-
-
R David Murray yazdı
This patch primarily does two things: (1) it adds some internal-interface methods to Policy that allow for Policy to control the parsing and folding of headers in such a way that we can construct a backward compatibility policy that is 100% compatible with the 3.2 API, while allowing a new policy to implement the email6 API. (2) it adds that backward compatibility policy and refactors the test suite so that the only differences between the 3.2 test_email.py file and the 3.3 test_email.py file is some small changes in test framework and the addition of tests for bugs fixed that apply to the 3.2 API. There are some additional teaks, such as moving just the code needed for the compatibility policy into _policybase, so that the library code can import only _policybase. That way the new code that will be added for email6 will only get imported when a non-compatibility policy is imported.
-
- 17 Mar, 2012 1 kayıt (commit)
-
-
R David Murray yazdı
Original patch by Steffen Daode Nurpmeso
-
- 22 Haz, 2011 1 kayıt (commit)
-
-
R David Murray yazdı
-
- 18 Nis, 2011 1 kayıt (commit)
-
-
R David Murray yazdı
This new interface will also allow for future planned enhancements in control over the parser/generator without requiring any additional complexity in the parser/generator API. Patch reviewed by Éric Araujo and Barry Warsaw.
-
- 15 Nis, 2011 1 kayıt (commit)
-
-
R David Murray yazdı
-
- 06 Nis, 2011 1 kayıt (commit)
-
-
R David Murray yazdı
Really the whole API needs to be gone over to restore the separation of concerns; but that's what email6 is about.
-
- 08 Eki, 2010 1 kayıt (commit)
-
-
R. David Murray yazdı
The work on this is not 100% complete, but everything is present to allow real-world testing of the code. The only remaining major todo item is to (hopefully!) enhance the handling of non-ASCII bytes in headers converted to unicode by RFC2047 encoding them rather than replacing them with '?'s.
-
- 17 Tem, 2010 4 kayıt (commit)
-
-
R. David Murray yazdı
svn+ssh://pythondev@svn.python.org/python/branches/release27-maint ................ r82924 | r.david.murray | 2010-07-16 21:35:16 -0400 (Fri, 16 Jul 2010) | 11 lines Merged revisions 82922 via svnmerge from svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r82922 | r.david.murray | 2010-07-16 21:19:57 -0400 (Fri, 16 Jul 2010) | 4 lines #1555570: correctly handle a \r\n that is split by the read buffer. Patch and test by Tony Nelson. ........ ................
-
R. David Murray yazdı
svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r82922 | r.david.murray | 2010-07-16 21:19:57 -0400 (Fri, 16 Jul 2010) | 4 lines #1555570: correctly handle a \r\n that is split by the read buffer. Patch and test by Tony Nelson. ........
-
R. David Murray yazdı
svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r82922 | r.david.murray | 2010-07-16 21:19:57 -0400 (Fri, 16 Jul 2010) | 4 lines #1555570: correctly handle a \r\n that is split by the read buffer. Patch and test by Tony Nelson. ........
-
R. David Murray yazdı
Patch and test by Tony Nelson.
-
- 16 Haz, 2010 3 kayıt (commit)
-
-
R. David Murray yazdı
svn+ssh://pythondev@svn.python.org/python/branches/py3k ................ r82011 | r.david.murray | 2010-06-15 22:19:40 -0400 (Tue, 15 Jun 2010) | 17 lines Merged revisions 81675 via svnmerge from svn+ssh://pythondev@svn.python.org/python/trunk ........ r81675 | r.david.murray | 2010-06-03 11:43:20 -0400 (Thu, 03 Jun 2010) | 10 lines #5610: use \Z not $ so we don't eat extra chars when body part ends with \r\n. If a body part ended with \r\n, feedparser, using '$' to terminate its search for the newline, would match on the \r\n, and think that it needed to strip two characters in order to account for the line end before the boundary. That made it chop one too many characters off the end of the body part. Using \Z makes the match correct. Patch and test by Tony Nelson. ........ ................
-
R. David Murray yazdı
svn+ssh://pythondev@svn.python.org/python/trunk ........ r81675 | r.david.murray | 2010-06-03 11:43:20 -0400 (Thu, 03 Jun 2010) | 10 lines #5610: use \Z not $ so we don't eat extra chars when body part ends with \r\n. If a body part ended with \r\n, feedparser, using '$' to terminate its search for the newline, would match on the \r\n, and think that it needed to strip two characters in order to account for the line end before the boundary. That made it chop one too many characters off the end of the body part. Using \Z makes the match correct. Patch and test by Tony Nelson. ........
-
R. David Murray yazdı
svn+ssh://pythondev@svn.python.org/python/trunk ........ r81675 | r.david.murray | 2010-06-03 11:43:20 -0400 (Thu, 03 Jun 2010) | 10 lines #5610: use \Z not $ so we don't eat extra chars when body part ends with \r\n. If a body part ended with \r\n, feedparser, using '$' to terminate its search for the newline, would match on the \r\n, and think that it needed to strip two characters in order to account for the line end before the boundary. That made it chop one too many characters off the end of the body part. Using \Z makes the match correct. Patch and test by Tony Nelson. ........
-
- 03 Haz, 2010 1 kayıt (commit)
-
-
R. David Murray yazdı
If a body part ended with \r\n, feedparser, using '$' to terminate its search for the newline, would match on the \r\n, and think that it needed to strip two characters in order to account for the line end before the boundary. That made it chop one too many characters off the end of the body part. Using \Z makes the match correct. Patch and test by Tony Nelson.
-
- 16 Eki, 2007 1 kayıt (commit)
-
-
Guido van Rossum yazdı
I like this because it makes the code shorter! :-)
-
- 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.
-
- 21 Nis, 2007 1 kayıt (commit)
-
-
Georg Brandl yazdı
-
- 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.
-
- 18 Mar, 2006 1 kayıt (commit)
-
-
Barry Warsaw yazdı
and NEWS updates.
-
- 17 Ock, 2006 1 kayıt (commit)
-
-
Barry Warsaw yazdı
Change headerRE as suggested in the bug report, so that single character headers are accepted. Test case added too. Will backport to Python 2.4.
-
- 05 Ara, 2004 1 kayıt (commit)
-
-
Barry Warsaw yazdı
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.
-
- 29 Kas, 2004 1 kayıt (commit)
-
-
Barry Warsaw yazdı
this, and add test cases.
-
- 28 Kas, 2004 1 kayıt (commit)
-
-
Barry Warsaw yazdı
in a newline, and it's an end boundary, the FeedParser wasn't recognizing it as such. Tweak the regexp to make the ending linesep optional. For grins, clear self._partial when closing the BufferedSubFile. Added a test case.
-
- 09 Eki, 2004 1 kayıt (commit)
-
-
Barry Warsaw yazdı
capturing_preamble but we found a StartBoundaryNotFoundDefect, we need to consume all lines from the current position to the EOF, which we'll set as the epilogue of the current message. If we're not at EOF when we return from here, the outer message's capturing_preamble assertion will fail.
-