[Python-bugs-list] [ python-Bugs-552345 ] rfc822.parsedate() too strict

noreply@sourceforge.net noreply@sourceforge.net
Mon, 30 Dec 2002 09:19:56 -0800


Bugs item #552345, was opened at 2002-05-04 16:53
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=552345&group_id=5470

Category: Python Library
Group: Python 2.3
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Barry A. Warsaw (bwarsaw)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: rfc822.parsedate() too strict

Initial Comment:
rfc822.parsedate('Wed,3 Apr 2002 14:58:26 +0800')
returns None.  Note the lack of space between the
command and the 3.  That space is actually optional in
RFC 2822, so it should parse the same as 
parsedate('Wed, 3 Apr 2002 14:58:26 +0800')


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-30 12:19

Message:
Logged In: YES 
user_id=12800

I'm actually not interested in fixing this for rfc822.py,
but I have a simpler patch for email.Utils._parseaddr, along
with a test case.  I'm going to check that in now.

----------------------------------------------------------------------

Comment By: Raymond Hettinger (rhettinger)
Date: 2002-08-19 00:39

Message:
Logged In: YES 
user_id=80475

Added a patch and unittest which fix the reported 
problem.  Tried to adopt a style of accurate 
implementation that can be extended when we get a 
chance.  The style is to use regular expressions which 
relate directly back to the rfc2822 specification.

If approved, re-assign back to me for a commit to Py2.3.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=552345&group_id=5470