From: Georg Brandl Date: Fri, 11 Jan 2008 12:58:40 +0000 (+0000) Subject: Fix markup. X-Git-Tag: v3.0a3~208 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=222e1279f8d4d271a74486081f77d7346ea93105;p=thirdparty%2FPython%2Fcpython.git Fix markup. --- diff --git a/Doc/library/string.rst b/Doc/library/string.rst index 41b8a497600e..7cd28b0db174 100644 --- a/Doc/library/string.rst +++ b/Doc/library/string.rst @@ -230,8 +230,8 @@ as a string, overriding its own definition of formatting. By converting the value to a string before calling :meth:`__format__`, the normal formatting logic is bypassed. -Two conversion flags are currently supported: ``'!s'`` which calls :func:`str()` -on the value, and ``'!r'`` which calls :func:`repr()`. +Two conversion flags are currently supported: ``'!s'`` which calls :func:`str` +on the value, and ``'!r'`` which calls :func:`repr`. Some examples:: @@ -289,7 +289,7 @@ Most built-in types implement the following options for format specifications, although some of the formatting options are only supported by the numeric types. A general convention is that an empty format string (``""``) produces the same -result as if you had called :func:`str()` on the value. +result as if you had called :func:`str` on the value. The general form of a *standard format specifier* is: