[issue10954] No warning for csv.writer API change

Skip Montanaro report at bugs.python.org
Sun Jan 23 23:17:34 CET 2011


Skip Montanaro <skip at pobox.com> added the comment:

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.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10954>
_______________________________________


More information about the Python-bugs-list mailing list