From: R David Murray Date: Sun, 20 Mar 2011 15:18:21 +0000 (-0400) Subject: Markup fixes for #7198 patch. X-Git-Tag: v3.2.1b1~248^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=9c0d5eaa705ca3ebaab395cc59d24d3b9c0289f4;p=thirdparty%2FPython%2Fcpython.git Markup fixes for #7198 patch. --- diff --git a/Doc/library/csv.rst b/Doc/library/csv.rst index 1dd8aa831ba7..92ba6da7d107 100644 --- a/Doc/library/csv.rst +++ b/Doc/library/csv.rst @@ -79,8 +79,8 @@ The :mod:`csv` module defines the following functions: 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 @@ -466,5 +466,5 @@ done:: .. [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.