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 skip.montanaro
Recipients Martin.Budaj, andrewmcnamara, ned.deily, r.david.murray, skip.montanaro
Date 2010-12-11.12:32:23
SpamBayes Score 3.02894e-10
Marked as misclassified No
Message-id <19715.28462.430900.259411@montanaro.dyndns.org>
In-reply-to <1292039214.4.0.299971646352.issue10515@psf.upfronthosting.co.za>
Content
From the comment in the test_csv.py:

+        # XXX: I don't know what the correct behavior should be for these.
+        # Currently the first one raises an error that the delimiter can't
+        # be determined while the second one returns '\r'.  The second
+        # is obviously.
+        ('"a,b,c,d"\ne',  ''),
+        ('"a,b,c,d"\r\ne', ''),

Obviously what?  My guess would be "wrong".  In the absence of any other
information \r\n has to be treated as a line separator.  It shouldn't be
considered as two separate characters, even in such a devoid-of-clues test
case.

Is the empty string a valid delimiter?  I've never tried it and it's been a
long time since I looked at any of the code.  I do use single-column CSV
files from time-to-time though.  I don't think a ',' would be a completely
unreasonable fallback scenario either.

Skip
History
Date User Action Args
2010-12-11 12:32:35skip.montanarosetrecipients: + skip.montanaro, andrewmcnamara, ned.deily, r.david.murray, Martin.Budaj
2010-12-11 12:32:23skip.montanarolinkissue10515 messages
2010-12-11 12:32:23skip.montanarocreate