From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Tue, 3 Oct 2023 06:20:20 +0000 (-0700) Subject: [3.12] Fix typo in py312 whatsnew: add missing closing paren (GH-110255) (#110257) X-Git-Tag: v3.12.1~394 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=64afbf6f2815d03ea8a94b64e6e45d5990413876;p=thirdparty%2FPython%2Fcpython.git [3.12] Fix typo in py312 whatsnew: add missing closing paren (GH-110255) (#110257) Fix typo in py312 whatsnew: add missing closing paren (GH-110255) (cherry picked from commit 8c071373f12f325c54591fe990ec026184e48f8f) Co-authored-by: Lele Gaifax --- diff --git a/Doc/whatsnew/3.12.rst b/Doc/whatsnew/3.12.rst index f9cc94514f2c..9080908c5c96 100644 --- a/Doc/whatsnew/3.12.rst +++ b/Doc/whatsnew/3.12.rst @@ -303,7 +303,7 @@ Let's cover these in detail: See :pep:`701` for more details. As a positive side-effect of how this feature has been implemented (by parsing f-strings -with :pep:`the PEG parser <617>`, now error messages for f-strings are more precise +with :pep:`the PEG parser <617>`), now error messages for f-strings are more precise and include the exact location of the error. For example, in Python 3.11, the following f-string raises a :exc:`SyntaxError`: