From 2c0a59bb3d2fb83312c965ea9d5ef9d0028a53bb Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Fri, 12 Jun 2020 06:01:20 -0700 Subject: [PATCH] Update lexical_analysis.rst (GH-17508) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Use Sphinx role markup for `str.format`. Automerge-Triggered-By: @csabella (cherry picked from commit e2fb8a2c42ee60c72a40d93da69e9efc4e359023) Co-authored-by: Géry Ogam --- Doc/reference/lexical_analysis.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/reference/lexical_analysis.rst b/Doc/reference/lexical_analysis.rst index e3a3a88757e..7d70cbcaa37 100644 --- a/Doc/reference/lexical_analysis.rst +++ b/Doc/reference/lexical_analysis.rst @@ -704,7 +704,7 @@ Top-level format specifiers may include nested replacement fields. These nested fields may include their own conversion fields and :ref:`format specifiers `, but may not include more deeply-nested replacement fields. The :ref:`format specifier mini-language ` is the same as that used by -the string .format() method. +the :meth:`str.format` method. Formatted string literals may be concatenated, but replacement fields cannot be split across literals.