➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: rfc822.parsedate() too strict
Type: Stage:
Components: Library (Lib) Versions: Python 2.3
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: barry Nosy List: barry, rhettinger
Priority: normal Keywords:

Created on 2002-05-04 20:53 by barry, last changed 2022-04-10 16:05 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
rfc822.diff rhettinger, 2002-08-19 04:39 Patch to rfc822.py
Messages (3)
msg10659 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2002-05-04 20:53 
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')
msg10660 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2002-08-19 04:39 
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.
msg10661 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2002-12-30 17:19 
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.
History
Date User Action Args
2022-04-10 16:05:17adminsetgithub: 36553
2002-05-04 20:53:32barrycreate