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 barry, ggenellina, ishimoto, jafo, kael, leromarinvit, r.david.murray, runtux, tkikuchi, tlynn, tony_nelson
Date 2012-01-02.18:14:26
SpamBayes Score 2.41079e-06
Marked as misclassified No
Message-id <>
The RFC isn't at all vague about encoded words not separated by white space.  That isn't allowed by the BNF.  As you say, though, they occur in the wild and should be parsed correctly.

In your other point I think you mean "immediately followed by a )", right?  Yes, that is allowed and no, we don't currently parse that correctly.

Adding the RFC tests would be great (patches gladly accepted).  Fixes for ones we fail would be great, too, but at the very least we can mark them as expected failures.  I don't usually like adding tests that we expect to fail, but in the case of externally defined tests such as the RFC examples I think it is worthwhile, so that we can check in a complete test set.
Date User Action Args
2012-01-02 18:14:27r.david.murraysetrecipients: + r.david.murray, barry, jafo, ishimoto, tlynn, ggenellina, tkikuchi, tony_nelson, kael, leromarinvit, runtux
2012-01-02 18:14:27r.david.murraysetmessageid: <>
2012-01-02 18:14:27r.david.murraylinkissue1079 messages
2012-01-02 18:14:26r.david.murraycreate