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 r.david.murray, vstinner
Date 2010-10-18.20:12:56
SpamBayes Score 5.94897e-10
Marked as misclassified No
Message-id <1287432778.96.0.347493673704.issue10134@psf.upfronthosting.co.za>
In-reply-to
Content
Here is a patch that adds a test of the underlying problem and fixes it.  I don't like this patch because it tries to detect the line ending style of the input stream and changes behavior based on that, but because email wants to use '\n' as the separator internally I don't see another way to fix it at the moment.  The ugliest part is that I changed the expected result of one existing test...but that test uses an artificial way of opening an input file in order to test the parser's universal newline handling, and I think the behavior tested is arguably incorrect.

I'm not sure this will fix all the windows failures, but it should fix most of them.
History
Date User Action Args
2010-10-18 20:12:59r.david.murraysetrecipients: + r.david.murray, vstinner
2010-10-18 20:12:58r.david.murraysetmessageid: <1287432778.96.0.347493673704.issue10134@psf.upfronthosting.co.za>
2010-10-18 20:12:57r.david.murraylinkissue10134 messages
2010-10-18 20:12:57r.david.murraycreate