1. 30 Agu, 2007 1 kayıt (commit)
  2. 25 Agu, 2007 1 kayıt (commit)
  3. 09 Agu, 2007 1 kayıt (commit)
    • Guido van Rossum's avatar
      SF patch# 1770008 by Christian Heimes (plus some extras). · 34d19287
      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.
      34d19287
  4. 21 Nis, 2006 1 kayıt (commit)
  5. 03 Eki, 2004 1 kayıt (commit)
    • Barry Warsaw's avatar
      Big email 3.0 API changes, with updated unit tests and documentation. · bb113867
      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.
      bb113867
  6. 09 May, 2004 1 kayıt (commit)
  7. 20 Mar, 2004 1 kayıt (commit)
    • Thomas Wouters's avatar
      Merge in Anthony's new parser code, from the anthony-parser-branch: · 0813d76c
      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.
      > =============================================================================
      0813d76c
  8. 06 Mar, 2003 1 kayıt (commit)
  9. 05 Kas, 2002 2 kayıt (commit)
    • Barry Warsaw's avatar
      parse(), _parseheaders(), _parsebody(): A fix for SF bug #633527, · da2525ed
      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.
      da2525ed
    • Barry Warsaw's avatar
      _parsebody(): A fix for SF bug #631350, where a subobject in a · 5c9130ec
      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.
      5c9130ec
  10. 07 Eki, 2002 1 kayıt (commit)
  11. 30 Eyl, 2002 1 kayıt (commit)
  12. 28 Eyl, 2002 1 kayıt (commit)
  13. 10 Eyl, 2002 1 kayıt (commit)
  14. 23 Agu, 2002 1 kayıt (commit)
  15. 19 Tem, 2002 1 kayıt (commit)
  16. 18 Tem, 2002 1 kayıt (commit)
    • Barry Warsaw's avatar
      Anthony Baxter's cleanup patch. Python project SF patch # 583190, · 7aeac918
      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 ;).
      7aeac918
  17. 09 Tem, 2002 1 kayıt (commit)
    • Barry Warsaw's avatar
      Anthony Baxter's patch for non-strict parsing. This adds a `strict' · f6caeba0
      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.
      f6caeba0
  18. 02 Haz, 2002 1 kayıt (commit)
  19. 19 May, 2002 1 kayıt (commit)
    • Barry Warsaw's avatar
      I've thought about it some more, and I believe it is proper for the · 7e21b679
      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.
      7e21b679
  20. 10 Nis, 2002 1 kayıt (commit)
  21. 27 Ock, 2002 1 kayıt (commit)
  22. 11 Eki, 2001 1 kayıt (commit)
  23. 04 Eki, 2001 2 kayıt (commit)
  24. 26 Eyl, 2001 1 kayıt (commit)
    • Barry Warsaw's avatar
      _parsebody(): Use get_boundary() and get_type(). · 66971fbc
      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.
      66971fbc
  25. 23 Eyl, 2001 1 kayıt (commit)