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 gvanrossum
Recipients georg.brandl, gvanrossum, jaywalker, jdwhitley, pitrou, sjmachin, skip.montanaro, vstinner
Date 2009-04-01.16:50:02
SpamBayes Score 7.37126e-08
Marked as misclassified No
Message-id <1238604604.68.0.975137847972.issue4847@psf.upfronthosting.co.za>
In-reply-to
Content
I think it's good if it allowed passing in a binary file and an
encoding, but I think it would be crazy if it wouldn't also take a text
file.  After all the primary purpose of a CSV file, edge cases
notwithstanding, is to look like text to the end user in a text editor
(as opposed to Excel spreadsheets, which look like binary gobbledygook
unless opened with Excel).

Are there any use cases for returning bytes strings instead of text
strings?  If so that should probably be another flag.
History
Date User Action Args
2009-04-01 16:50:04gvanrossumsetrecipients: + gvanrossum, skip.montanaro, georg.brandl, sjmachin, pitrou, vstinner, jaywalker, jdwhitley
2009-04-01 16:50:04gvanrossumsetmessageid: <1238604604.68.0.975137847972.issue4847@psf.upfronthosting.co.za>
2009-04-01 16:50:03gvanrossumlinkissue4847 messages
2009-04-01 16:50:02gvanrossumcreate