1e9cc3d502
gh-133197: Improve error message for incompatible string / bytes prefixes ( #133242 )
2025-05-02 14:28:17 +03:00
60202609a2
gh-132661: Implement PEP 750 ( #132662 )
...
Co-authored-by: Lysandros Nikolaou <lisandrosnik@gmail.com>
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Wingy <git@wingysam.xyz>
Co-authored-by: Koudai Aono <koxudaxi@gmail.com>
Co-authored-by: Dave Peck <davepeck@gmail.com>
Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu>
Co-authored-by: Paul Everitt <pauleveritt@me.com>
Co-authored-by: sobolevn <mail@sobolevn.me>
2025-04-30 11:46:41 +02:00
2f8b08da47
gh-129958: Properly disallow newlines in format specs in single-quoted f-strings (GH-130063)
2025-04-18 14:30:04 +02:00
014223649c
GH-130396: Use computed stack limits on linux (GH-130398)
...
* Implement C recursion protection with limit pointers for Linux, MacOS and Windows
* Remove calls to PyOS_CheckStack
* Add stack protection to parser
* Make tests more robust to low stacks
* Improve error messages for stack overflow
2025-02-25 09:24:48 +00:00
ef29104f7d
GH-91079: Revert "GH-91079: Implement C stack limits using addresses, not counters. (GH-130007)" for now (GH130413)
...
Revert "GH-91079: Implement C stack limits using addresses, not counters. (GH-130007)" for now
Unfortunatlely, the change broke some buildbots.
This reverts commit 2498c22fa0
2025-02-24 11:16:08 +01:00
2498c22fa0
GH-91079: Implement C stack limits using addresses, not counters. (GH-130007)
...
* Implement C recursion protection with limit pointers
* Remove calls to PyOS_CheckStack
* Add stack protection to parser
* Make tests more robust to low stacks
* Improve error messages for stack overflow
2025-02-19 11:44:57 +00:00
2dd018848c
gh-129693: Suppress `SyntaxWarning` in test_fstring ( #129830 )
...
Suppress SyntaxWarning in test_fstring
2025-02-13 00:38:28 +00:00
60a3a0dd6f
gh-124363: Treat debug expressions in f-string as raw strings ( #128399 )
...
Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com>
2025-01-22 16:24:54 +00:00
767cf70844
gh-129093: Fix f-string debug text sometimes getting cut off when expression contains `!` ( #129159 )
2025-01-22 00:26:37 +00:00
9017b95ff2
Fix typos ( #123775 )
2024-09-09 14:58:26 +02:00
2009e25e26
gh-122026: Fix identification of mismatched parentheses inside f-strings ( #122028 )
2024-07-19 19:08:08 +02:00
c46d64e0ef
gh-121130: Fix f-string format specifiers with debug expressions ( #121150 )
2024-07-16 19:57:22 +01:00
5a8a979aeb
gh-120417: Remove unused imports in tests (part 2) ( #120630 )
2024-06-17 21:05:37 +02:00
fb202af447
gh-99606: Make code generated for an empty f-string identical to that of a normal empty string ( #112407 )
2023-11-26 17:13:57 +00:00
d59feb5dbe
gh-112243: Don't include comments in f-string debug expressions ( #112284 )
2023-11-20 15:18:24 +00:00
2cb62c6437
gh-110309: Prune empty constant in format specs ( #110320 )
...
Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com>
2023-10-05 14:08:42 +00:00
5bda2f637e
gh-109114: Relax the check for invalid lambdas inside f-strings to avoid false positives ( #109121 )
2023-09-08 17:00:23 +00:00
d66bc9e8a7
gh-107967: Fix infinite recursion on invalid escape sequence warning ( #107968 )
2023-08-15 11:26:42 +00:00
dfe4de2038
gh-106396: Special-case empty format spec to gen empty JoinedStr node ( #106401 )
2023-07-04 14:19:08 +02:00
6e40ee6e84
gh-105915: Fix SyntaxWarning becoming a SyntaxError with -We in test_fstring ( #105943 )
2023-06-20 16:13:07 +02:00
4b431d2e90
gh-105915: Add 'r' prefix to not emit SyntaxWarning in test_fstring ( #105940 )
...
Co-authored-by: @sunmy2019
2023-06-20 14:49:00 +02:00
6586cee27f
gh-105938: Emit a SyntaxWarning for escaped braces in an f-string ( #105939 )
2023-06-20 12:38:46 +00:00
d382ad4915
gh-105820: Fix tok_mode expression buffer in file & readline tokenizer ( #105828 )
2023-06-15 16:21:24 +00:00
12b6d844d8
gh-105800: Issue SyntaxWarning in f-strings for invalid escape sequences ( #105801 )
2023-06-15 01:08:12 +01:00
41de54378d
gh-105194: Fix format specifier escaped characters in f-strings ( #105231 )
2023-06-02 13:33:26 +02:00
0a7796052a
gh-102856: Allow comments inside multi-line f-string expresions ( #104006 )
2023-05-22 10:30:07 +00:00
ff7f731632
gh-104658: Fix location of unclosed quote error for multiline f-strings ( #104660 )
2023-05-20 14:07:05 +01:00
83751bbd14
gh-104089: catch DeprecationWarning in `test_fstring` ( #104137 )
...
Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>
2023-05-04 11:20:20 +01:00
b1ca34d4d5
gh-104016: Skip test for deeply neste f-strings on wasi ( #104071 )
2023-05-01 23:55:41 +00:00
5078eedc5b
gh-104016: Fixed off by 1 error in f string tokenizer ( #104047 )
...
Co-authored-by: sunmy2019 <59365878+sunmy2019@users.noreply.github.com>
Co-authored-by: Ken Jin <kenjin@python.org>
Co-authored-by: Pablo Galindo <pablogsal@gmail.com>
2023-05-01 19:15:47 +00:00
9169a56fad
gh-103656: Transfer f-string buffers to parser to avoid use-after-free (GH-103896)
...
Co-authored-by: Pablo Galindo <pablogsal@gmail.com>
2023-04-27 01:33:31 +00:00
cb157a1a35
GH-103727: Avoid advancing tokenizer too far in f-string mode (GH-103775)
2023-04-24 12:30:21 -06:00
05b3ce7339
GH-103718: Correctly cache and restore f-string buffers when needed (GH-103719)
2023-04-23 13:06:10 -06:00
5f7d68e48d
gh-102856: Skip test_mismatched_parens in WASI builds ( #103633 )
2023-04-19 11:53:34 -06:00
1ef61cf71a
gh-102856: Initial implementation of PEP 701 ( #102855 )
...
Co-authored-by: Lysandros Nikolaou <lisandrosnik@gmail.com>
Co-authored-by: Batuhan Taskaya <isidentical@gmail.com>
Co-authored-by: Marta Gómez Macías <mgmacias@google.com>
Co-authored-by: sunmy2019 <59365878+sunmy2019@users.noreply.github.com>
2023-04-19 11:18:16 -05:00
3eb12df8b5
Fix typo in test_fstring.py ( #101823 )
2023-02-11 21:04:15 +05:30
272da55aff
Fix typo in `test_fstring.py` ( #101600 )
2023-02-09 23:15:58 +05:30
a60ddd31be
gh-98401: Invalid escape sequences emits SyntaxWarning ( #99011 )
...
A backslash-character pair that is not a valid escape sequence now
generates a SyntaxWarning, instead of DeprecationWarning. For
example, re.compile("\d+\.\d+") now emits a SyntaxWarning ("\d" is an
invalid escape sequence), use raw strings for regular expression:
re.compile(r"\d+\.\d+"). In a future Python version, SyntaxError will
eventually be raised, instead of SyntaxWarning.
Octal escapes with value larger than 0o377 (ex: "\477"), deprecated
in Python 3.11, now produce a SyntaxWarning, instead of
DeprecationWarning. In a future Python version they will be
eventually a SyntaxError.
codecs.escape_decode() and codecs.unicode_escape_decode() are left
unchanged: they still emit DeprecationWarning.
* The parser only emits SyntaxWarning for Python 3.12 (feature
version), and still emits DeprecationWarning on older Python
versions.
* Fix SyntaxWarning by using raw strings in Tools/c-analyzer/ and
wasm_build.py.
2022-11-03 17:53:25 +01:00
2e9da8e352
gh-94869: Fix the location in some expressions for multi-line f-string ast nodes ( #94895 )
2022-07-16 19:51:53 +01:00
ee70c70aa9
gh-93418: Fix an assert when an f-string expression is followed by an '=', but no closing brace. (gh-93419)
2022-06-01 19:20:06 -04:00
07df8d5b2c
gh-93283: Improve error message for f-string with invalid conversion character (GH-93349)
2022-05-31 20:38:29 +03:00
7b44ade018
bpo-47129: Add more informative messages to f-string syntax errors (32127)
...
* Add more informative messages to f-string syntax errors
* 📜 🤖 Added by blurb_it.
* Fix whitespaces
* Change error message
* Remove the 'else' statement (as sugested in review)
Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com>
2022-03-28 17:08:36 -04:00
ffd9f8ff84
bpo-46762: Fix an assert failure in f-strings where > or < is the last character if the f-string is missing a trailing right brace. ( #31365 )
2022-02-16 05:54:09 -05:00
0daf72194b
bpo-46503: Prevent an assert from firing when parsing some invalid \N sequences in f-strings. (GH-30865)
...
* bpo-46503: Prevent an assert from firing. Also fix one nearby tiny PEP-7 nit.
* Added blurb.
2022-01-24 21:53:27 -05:00
24c10d2943
bpo-45727: Only trigger the 'did you forgot a comma' error suggestion if inside parentheses (GH-29757)
2021-11-24 22:21:23 +00:00
8e832fb2a2
bpo-44885: Correct the ast locations of f-strings with format specs and repeated expressions (GH-27729)
2021-08-12 17:13:30 +01:00
b86ed8e3bb
bpo-43797: Improve syntax error for invalid comparisons ( #25317 )
...
* bpo-43797: Improve syntax error for invalid comparisons
* Update Lib/test/test_fstring.py
Co-authored-by: Guido van Rossum <gvanrossum@gmail.com>
* Apply review comments
* can't -> cannot
Co-authored-by: Guido van Rossum <gvanrossum@gmail.com>
2021-04-12 16:59:30 +01:00
3caea9adda
bpo-43651: PEP 597: Fix EncodingWarning in some tests (GH-25171)
...
* Fix test_float
* Fix _osx_support
* Fix test_fstring
* Fix test_gc
* Fix test_gzip
* Fix test_hashlib
* Fix unrelated whitespace issue
Co-authored-by: Ned Deily <nad@python.org>
2021-04-04 17:01:10 +09:00
8efad61963
bpo-41064: Improve syntax error for invalid usage of '**' in f-strings (GH-25006)
2021-03-24 19:34:17 +00:00
4090151816
bpo-42986: Fix parser crash when reporting syntax errors in f-string with newlines (GH-24279)
2021-01-31 22:48:23 +00:00
sobolevn