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 georg.brandl, jaywalker, jdwhitley, pitrou, sjmachin, skip.montanaro, vstinner
Date 2009-03-10.10:42:55
SpamBayes Score 0.0007191092
Marked as misclassified No
Message-id <1236681777.82.0.389073201039.issue4847@psf.upfronthosting.co.za>
In-reply-to
Content
This issue seems to have simply been overlooked when 3.0 was released.
It should be fixed in the next round of 3.0 and 3.1 updates.  Any
feeback on the idea that the csv.reader constructor (and probably the
DictReader and proposed NamedTupleReader constructors) should take an
optional encoding argument?  In fact, the writers should as well
which would inform the writer how to encode the output when writing.
History
Date User Action Args
2009-03-10 10:42:58skip.montanarosetrecipients: + skip.montanaro, georg.brandl, sjmachin, pitrou, vstinner, jaywalker, jdwhitley
2009-03-10 10:42:57skip.montanarosetmessageid: <1236681777.82.0.389073201039.issue4847@psf.upfronthosting.co.za>
2009-03-10 10:42:56skip.montanarolinkissue4847 messages
2009-03-10 10:42:55skip.montanarocreate