➜

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 keef604
Recipients Mariatta, keef604, peter.otten, r.david.murray, rhettinger
Date 2017-04-11.13:52:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1491918736.72.0.497627461849.issue30034@psf.upfronthosting.co.za>
In-reply-to
Content 
The csv reader already supports bad CSV - that's what I believe "strict" is for - but only in one specific scenario.  My request is to make that "strict" attribute a bit more useful.

Thank you for your suggestion, Peter.  I have toyed with the idea of looking for an even number of double quotes in each line, but thank you for your neat way of encapsulating it.  (I already have to strip null bytes out of the input data because they break csv, see issue #27580).
History
Date User Action Args
2017-04-11 13:52:16keef604setrecipients: + keef604, rhettinger, peter.otten, r.david.murray, Mariatta
2017-04-11 13:52:16keef604setmessageid: <1491918736.72.0.497627461849.issue30034@psf.upfronthosting.co.za>
2017-04-11 13:52:16keef604linkissue30034 messages
2017-04-11 13:52:16keef604create