R. David Murray rdmur...@bitdance.com added the comment:
Instead of doing this we've opted to follow postel and be generous in what we
accept and go ahead and decode even if the leading and/or terminating space is
missing (see issue 1079).
--
resolution: - rejected
status: open -
Changes by R. David Murray rdmur...@bitdance.com:
--
assignee: r.david.murray -
components: +email
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9967
___
Changes by R. David Murray rdmur...@bitdance.com:
--
versions: +Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9967
___
___
Changes by R. David Murray rdmur...@bitdance.com:
--
versions: +Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9967
___
___
Changes by R. David Murray rdmur...@bitdance.com:
--
assignee: - r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9967
___
___
Changes by Ned Deily n...@acm.org:
--
nosy: +barry, r.david.murray
stage: - patch review
versions: -Python 2.5, Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9967
___
New submission from Tokio Kikuchi tkiku...@users.sourceforge.net:
Regular expression ecre for RFC2047 encoded_word in email.header module have
bugs:
1. encoded_word should be separated by SPACEs in both leading and trailing
ends. Current expression take care only trailing end.
2.
