Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | gh-101400: Fix incorrect lineno in exception message on continue/break which ↵ | Dong-hee Na | 2023-01-30 |
| | | | | are not in a loop (#101413) | ||
* | gh-100050: Fix an assertion error when raising unclosed parenthesis errors ↵ | Pablo Galindo Salgado | 2022-12-06 |
| | | | | | in the tokenizer (GH-100065) Automerge-Triggered-By: GH:pablogsal | ||
* | gh-90994: Improve error messages upon call arguments syntax errors (GH-96893) | Lysandros Nikolaou | 2022-11-21 |
| | |||
* | gh-99211: Point to except/except* on syntax errors when mixing them (GH-99215) | Lysandros Nikolaou | 2022-11-20 |
| | | | Automerge-Triggered-By: GH:lysnikolaou | ||
* | gh-99153: set location on SyntaxError for try with both except and except* ↵ | Irit Katriel | 2022-11-06 |
| | | | | (GH-99160) | ||
* | gh-98931: Improve error message when the user types 'import x from y' ↵ | Pablo Galindo Salgado | 2022-11-01 |
| | | | | instead of 'from y import x' (#98932) | ||
* | gh-91210: Improve error message when non-default param follows default ↵ | Lysandros Nikolaou | 2022-09-17 |
| | | | | | | (GH-95933) - Improve error message when parameter without a default follows one with a default - Show same error message when positional-only params precede the default/non-default sequence | ||
* | GH-95150: Use position and exception tables for code hashing and equality ↵ | Brandt Bucher | 2022-08-01 |
| | | | | (GH-95509) | ||
* | gh-94192: Fix error for dictionary literals with invalid expression as ↵ | wookie184 | 2022-06-26 |
| | | | | | | | value. (#94304) * Fix error for dictionary literals with invalid expression as value. * Remove trailing whitespace | ||
* | gh-92858: Improve error message for some suites with syntax error before ':' ↵ | wookie184 | 2022-06-23 |
| | | | | (#92894) | ||
* | bpo-47212: Improve error messages for un-parenthesized generator expressions ↵ | Matthieu Dartiailh | 2022-04-05 |
| | | | | (GH-32302) | ||
* | bpo-43224: Implement PEP 646 grammar changes (GH-31018) | Matthew Rahtz | 2022-03-26 |
| | | | Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com> | ||
* | bpo-46838: Syntax error improvements for function definitions (GH-31590) | Pablo Galindo Salgado | 2022-03-22 |
| | |||
* | Remove trailing spaces (GH-31695) | Serhiy Storchaka | 2022-03-05 |
| | |||
* | bpo-46707: Avoid potential exponential backtracking in some syntax errors ↵ | Pablo Galindo Salgado | 2022-02-10 |
| | | | | (GH-31241) | ||
* | bpo-46091: Correctly calculate indentation levels for whitespace lines with ↵ | Pablo Galindo Salgado | 2022-01-25 |
| | | | | continuation characters (GH-30130) | ||
* | bpo-46240: Correct the error for unclosed parentheses when the tokenizer is ↵ | Pablo Galindo Salgado | 2022-01-04 |
| | | | | not finished (GH-30378) | ||
* | bpo-46110: Restore commit e9898bf153d26059261ffef11f7643ae991e2a4c | Pablo Galindo Salgado | 2022-01-03 |
| | | | This restores commit e9898bf153d26059261ffef11f7643ae991e2a4c . | ||
* | Revert "bpo-46110: Add a recursion check to avoid stack overflow in the PEG ↵ | Pablo Galindo Salgado | 2022-01-03 |
| | | | | | parser (GH-30177)" (GH-30363) This reverts commit e9898bf153d26059261ffef11f7643ae991e2a4c temporarily as we want to confirm if this commit is the cause of a slowdown at startup time. | ||
* | bpo-46110: Add a recursion check to avoid stack overflow in the PEG parser ↵ | Pablo Galindo Salgado | 2021-12-20 |
| | | | | | (GH-30177) Co-authored-by: Batuhan Taskaya <isidentical@gmail.com> | ||
* | bpo-45292: [PEP-654] add except* (GH-29581) | Irit Katriel | 2021-12-14 |
| | |||
* | bpo-45811: Improve error message when source code contains invisible control ↵ | Pablo Galindo Salgado | 2021-11-20 |
| | | | | characters (GH-29654) | ||
* | bpo-45450: Improve syntax error for parenthesized arguments (GH-28906) | Pablo Galindo Salgado | 2021-11-20 |
| | |||
* | bpo-45738: Fix computation of error location for invalid continuation (GH-29550) | Pablo Galindo Salgado | 2021-11-14 |
| | | | characters in the parser | ||
* | bpo-45764: improve error message when missing '(' after 'def' (GH-29484) | Carl Friedrich Bolz-Tereick | 2021-11-09 |
| | | | | | to achieve this, change the grammar to expect the '(' token after 'def' NAME. Automerge-Triggered-By: GH:pablogsal | ||
* | bpo-45716: Improve the error message when using True/False/None as keywords ↵ | Pablo Galindo Salgado | 2021-11-05 |
| | | | | in a call (GH-29413) | ||
* | Remove trailing spaces. (GH-28706) | Serhiy Storchaka | 2021-10-03 |
| | |||
* | bpo-43914: Correctly highlight SyntaxError exceptions for invalid generator ↵ | Pablo Galindo Salgado | 2021-09-27 |
| | | | | expression in function calls (GH-28576) | ||
* | bpo-45229: Use doctest.DocTestSuite instead of run_doctest (GH-28468) | Serhiy Storchaka | 2021-09-20 |
| | | | Alo use load_tests() for adding tests. | ||
* | bpo-25130: Make unit-test about restricting the maximum number of nested ↵ | Carl Friedrich Bolz-Tereick | 2021-08-28 |
| | | | | | | | | blocks cpython-only (GH-28002) PyPy and potentially other implementations have different or no contraints on the number of blocks that can be statically nested. move the test that checks for this behaviour into a unit test and mark it as CPython-only. | ||
* | bpo-45000: Raise SyntaxError when try to delete __debug__ (GH-27947) | Dong-hee Na | 2021-08-25 |
| | | | Automerge-Triggered-By: GH:pablogsal | ||
* | bpo-44947: Refine the syntax error for trailing commas in import statements ↵ | Pablo Galindo Salgado | 2021-08-18 |
| | | | | (GH-27814) | ||
* | bpo-44838: Refine the custom syntax errors for invalid 'if' expressions ↵ | Pablo Galindo Salgado | 2021-08-05 |
| | | | | (GH-27615) | ||
* | bpo-44792: Improve syntax errors for if expressions (GH-27506) | Miguel Brito | 2021-08-02 |
| | |||
* | Remove unnecessary 'invalid_primary' rule in the parser (GH-27186) | Pablo Galindo Salgado | 2021-07-16 |
| | |||
* | bpo-44456: Improve the syntax error when mixing keyword and positional ↵ | Pablo Galindo | 2021-06-24 |
| | | | | patterns (GH-26793) | ||
* | bpo-44368: Improve syntax errors with invalid as pattern targets (GH-26632) | Pablo Galindo | 2021-06-10 |
| | |||
* | bpo-44368: Ensure we don't raise incorrect custom syntax errors with soft ↵ | Pablo Galindo | 2021-06-09 |
| | | | | keywords (GH-26630) | ||
* | bpo-44305: Improve syntax error for try blocks without except or finally ↵ | Pablo Galindo | 2021-06-03 |
| | | | | (GH-26523) | ||
* | bpo-44273: Improve syntax error message for assigning to "..." (GH-26477) | Serhiy Storchaka | 2021-06-01 |
| | | | Use "ellipsis" instead of "Ellipsis" in syntax error messages to eliminate confusion with built-in variable Ellipsis. | ||
* | bpo-44180: Fix edge cases in invalid assigment rules in the parser (GH-26283) | Pablo Galindo | 2021-05-21 |
| | | | | | | | | | | | | | | | The invalid assignment rules are very delicate since the parser can easily raise an invalid assignment when a keyword argument is provided. As they are very deep into the grammar tree, is very difficult to specify in which contexts these rules can be used and in which don't. For that, we need to use a different version of the rule that doesn't do error checking in those situations where we don't want the rule to raise (keyword arguments and generator expressions). We also need to check if we are in left-recursive rule, as those can try to eagerly advance the parser even if the parse will fail at the end of the expression. Failing to do this allows the parser to start parsing a call as a tuple and incorrectly identify a keyword argument as an invalid assignment, before it realizes that it was not a tuple after all. | ||
* | bpo-44168: Fix error message in the parser for keyword arguments for invalid ↵ | Pablo Galindo | 2021-05-19 |
| | | | | expressions (GH-26210) | ||
* | bpo-43149: Correct the syntax error message for multiple exception types ↵ | Pablo Galindo | 2021-05-08 |
| | | | | | (GH-25996) Automerge-Triggered-By: GH:pablogsal | ||
* | bpo-44063: set the missing end locations on the compiler (GH-25956) | Batuhan Taskaya | 2021-05-07 |
| | |||
* | bpo-43914: Highlight invalid ranges in SyntaxErrors (#25525) | Pablo Galindo | 2021-04-23 |
| | | | | | | | | | | | | | | | | | To improve the user experience understanding what part of the error messages associated with SyntaxErrors is wrong, we can highlight the whole error range and not only place the caret at the first character. In this way: >>> foo(x, z for z in range(10), t, w) File "<stdin>", line 1 foo(x, z for z in range(10), t, w) ^ SyntaxError: Generator expression must be parenthesized becomes >>> foo(x, z for z in range(10), t, w) File "<stdin>", line 1 foo(x, z for z in range(10), t, w) ^^^^^^^^^^^^^^^^^^^^ SyntaxError: Generator expression must be parenthesized | ||
* | bpo-43859: Improve the error message for IndentationError exceptions (GH-25431) | Pablo Galindo | 2021-04-21 |
| | |||
* | bpo-38605: Revert making 'from __future__ import annotations' the default ↵ | Pablo Galindo | 2021-04-21 |
| | | | | | | (GH-25490) This reverts commits 044a1048ca93d466965afc027b91a5a9eb9ce23c and 1be456ae9d53bb1cba2b24fc86175c282d1c2169, adapting the code to changes that happened after it. | ||
* | bpo-43822: Improve syntax errors for missing commas (GH-25377) | Pablo Galindo | 2021-04-15 |
| | |||
* | bpo-43823: Improve syntax errors for invalid dictionary literals (GH-25378) | Pablo Galindo | 2021-04-15 |
| | |||
* | bpo-43797: Handle correctly invalid assignments inside function calls and ↵ | Pablo Galindo | 2021-04-13 |
| | | | | generators (GH-25390) |