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 runtux
Recipients BreamoreBoy, alexanderweb, barry, georg.brandl, mgoutell, r.david.murray, runtux
Date 2012-01-02.15:50:43
SpamBayes Score 8.305971e-08
Marked as misclassified No
Message-id <>
I've been bitten by this too (in python up to 2.7 in roundup the bug-tracker). We're currently using a workaround that re-inserts spaces, see git on file method _decode_header_to_utf8

RFC2047 even has a test-case at the end, it specifies:

encoded form                                displayed as
(=?ISO-8859-1?Q?a?= b)                      (a b)

note the space between 'a' and 'b' above. Spaces between non-encoded and encoded parts should be preserved. And it's probably a good idea to put the examples from the RFC into the regression test.
Date User Action Args
2012-01-02 15:50:44runtuxsetrecipients: + runtux, barry, georg.brandl, alexanderweb, mgoutell, r.david.murray, BreamoreBoy
2012-01-02 15:50:44runtuxsetmessageid: <>
2012-01-02 15:50:44runtuxlinkissue1467619 messages
2012-01-02 15:50:43runtuxcreate