Message126903
| Author | skip.montanaro |
|---|---|
| Recipients | georg.brandl, lregebro, r.david.murray, sjmachin, skip.montanaro, terry.reedy |
| Date | 2011-01-23.22:17:33 |
| SpamBayes Score | 2.5900295e-05 |
| Marked as misclassified | No |
| Message-id | <1295821054.06.0.316824847826.issue10954@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Looking at the csv.rst file I see this statement early in the py3k
docs:
If *csvfile* is a file object, it should be opened with ``newline=''``.
There is also a footnote about the consequences of leaving it out:
.. [#] If ``newline=''`` is not specified, newlines embedded inside quoted fields
will not be interpreted correctly. It should always be safe to specify
``newline=''``, since the csv module does its own universal newline handling
on input.
Finally, the examples all use "newline=''". I see two things to change
in the docs:
* Replace "should" with "must" in the first quoted sentence above.
* Add that sentence to the documentation for the csv.writer()
function. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-01-23 22:17:34 | skip.montanaro | set | recipients: + skip.montanaro, georg.brandl, terry.reedy, sjmachin, lregebro, r.david.murray |
| 2011-01-23 22:17:34 | skip.montanaro | set | messageid: <1295821054.06.0.316824847826.issue10954@psf.upfronthosting.co.za> |
| 2011-01-23 22:17:33 | skip.montanaro | link | issue10954 messages |
| 2011-01-23 22:17:33 | skip.montanaro | create | |