[Python-checkins] cpython (merge 3.1 -> 3.2): Merge markup fixes for #7198 patch.

r.david.murray python-checkins at python.org
Sun Mar 20 16:40:10 CET 2011


http://hg.python.org/cpython/rev/d0d1235cb66e
changeset:   68753:d0d1235cb66e
branch:      3.2
parent:      68747:fa0563f3b7f7
parent:      68752:88876a264ebe
user:        R David Murray <rdmurray at bitdance.com>
date:        Sun Mar 20 11:19:20 2011 -0400
summary:
  Merge markup fixes for #7198 patch.

files:
  Doc/library/csv.rst

diff --git a/Doc/library/csv.rst b/Doc/library/csv.rst
--- a/Doc/library/csv.rst
+++ b/Doc/library/csv.rst
@@ -79,8 +79,8 @@
 
    Return a writer object responsible for converting the user's data into delimited
    strings on the given file-like object.  *csvfile* can be any object with a
-   :func:`write` method.  If csvfile is a file object, it should be opened with
-   newline='' [1]_.  An optional *dialect*
+   :func:`write` method.  If *csvfile* is a file object, it should be opened with
+   ``newline=''`` [1]_.  An optional *dialect*
    parameter can be given which is used to define a set of parameters specific to a
    particular CSV dialect.  It may be an instance of a subclass of the
    :class:`Dialect` class or one of the strings returned by the
@@ -485,5 +485,5 @@
 
 .. [1] If ``newline=''`` is not specified, newlines embedded inside quoted fields
    will not be interpreted correctly, and on platforms that use ``\r\n`` linendings
-   on write an extra `\\r` will be added.  It should always be safe to specify
+   on write an extra ``\r`` will be added.  It should always be safe to specify
    ``newline=''``, since the csv module does its own (universal) newline handling.

-- 
Repository URL: http://hg.python.org/cpython


More information about the Python-checkins mailing list