diff options
| author | Lele Gaifax <lele@metapensiero.it> | 2023-10-03 06:10:16 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-03 06:10:16 (GMT) |
| commit | 8c071373f12f325c54591fe990ec026184e48f8f (patch) | |
| tree | e41bedd9f1be535bea830d5ec955d86278f2df0a | |
| parent | 1001233fe16a02f70ca9bccf66b018cc63fe784c (diff) | |
| download | cpython-8c071373f12f325c54591fe990ec026184e48f8f.zip cpython-8c071373f12f325c54591fe990ec026184e48f8f.tar.gz cpython-8c071373f12f325c54591fe990ec026184e48f8f.tar.bz2 | |
Fix typo in py312 whatsnew: add missing closing paren (#110255)
| -rw-r--r-- | Doc/whatsnew/3.12.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/whatsnew/3.12.rst b/Doc/whatsnew/3.12.rst index 6fe00bb..78ebe6e 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`: |