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 georg.brandl, gvanrossum, jaywalker, jdwhitley, pitrou, r.david.murray, r.david.murray, sjmachin, skip.montanaro, vstinner
Date 2009-04-02.18:41:46
SpamBayes Score 3.330669e-16
Marked as misclassified No
Message-id <Pine.LNX.4.64.0904021433100.26362@kimball.webabinitio.net>
In-reply-to <18900.64521.455016.305184@montanaro.dyndns.org>
Content
On Thu, 2 Apr 2009 at 17:55, Skip Montanaro wrote:
> This thread is getting a bit long.  Can someone summarize how the expected
> usage of the csv module is supposed to change?  If I read things correctly,
> instead of requiring (in the general case) that csv files be opened in
> binary mode, the requirement will be that they be opened with newline=''.
> This will thwart any attempts by the io module at newline translation, but
> since the file is still opened in text mode its contents will implicitly be
> Unicode (or Unicode translated to bytes with a specific encoding).  That
> encoding will also be specified in the call to open().

I believe that is an accurate summary.

> Is this about correct?  Do any test cases need to be updated or added?  I
> notice that something called BytesIO is imported from io but not used.  Were
> some test cases removed which used to involve that class or is that a 2to3
> artifact?

I will look in to this, and add an encoding example to the docs as you
suggest in another email.

--David
History
Date User Action Args
2009-04-02 18:41:49r.david.murray-oldsetrecipients: + r.david.murray-old, gvanrossum, skip.montanaro, georg.brandl, sjmachin, pitrou, vstinner, r.david.murray, jaywalker, jdwhitley
2009-04-02 18:41:47r.david.murray-oldlinkissue4847 messages
2009-04-02 18:41:46r.david.murray-oldcreate