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.

Author r.david.murray
Recipients BreamoreBoy, alexanderweb, barry, georg.brandl, mgoutell, r.david.murray
Date 2010-08-23.01:25:59
SpamBayes Score 6.285165e-06
Marked as misclassified No
Message-id <1282526761.45.0.211712100875.issue1467619@psf.upfronthosting.co.za>
In-reply-to
Content
Georg's patch no longer applies to py3k.  I ported it, but the result is not functional.  It causes extra spaces during header generation, because it is there that email4/5 "deals" with "ignoring" spaces between encoded words by *adding* spaces when they are adjacent to non-encoded words.  (In general email4/5 compresses runs of whitespace into single spaces.)  I tried fixing that, but then ran in to the fact that header parsing/generation currently depends on the whitespace compression in order to handle the header folding cases.  So, the logic used for header parsing and generation in emai5 does not allow for an easy patch to fix this bug.  I'm deferring it to email6, where I an rewriting the header parser/generator.
History
Date User Action Args
2010-08-23 01:26:01r.david.murraysetrecipients: + r.david.murray, barry, georg.brandl, alexanderweb, mgoutell, BreamoreBoy
2010-08-23 01:26:01r.david.murraysetmessageid: <1282526761.45.0.211712100875.issue1467619@psf.upfronthosting.co.za>
2010-08-23 01:26:00r.david.murraylinkissue1467619 messages
2010-08-23 01:25:59r.david.murraycreate