On 11/8/07, Guido van Rossum <report@bugs.python.org> wrote:
> I do think there is something iffy here -- the 2.x version of this
> test opens the files in binary mode. I wonder what end users are
> supposed to do.

I think that requirement (need to open in binary mode) is no more
present in 3.0. As per revision 56777 (#1767398), csv module seems to
support unicode strings and as such I would expect that files *should
not* be opened in binary mode (This requires doc change both in csv
doc and "what's new in 3.0). The tests in test_csv are explicitly
writing "\r\n" which seems to be a hangover from 2.x. We seem to have
side-stepped the problem by passing "newline=''" at some places but
the real fix may be changing "\r\n"s to "\n" now that the temp files
are being opened in text mode.