Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | [3.8] bpo-37830: Fix compilation of break and continue in finally. ↵ | Serhiy Storchaka | 2019-08-24 | 1 | -0/+54 |
| | | | | | | | | | (GH-15320) (GH-15456) Fix compilation of "break" and "continue" in the "finally" block when the corresponding "try" block contains "return" with a non-constant value. (cherry picked from commit ef61c524ddeeb56da3858b86e349e7288d68178e) | ||||
* | bpo-35814: Allow unpacking in r.h.s of annotated assignment expressions ↵ | Pablo Galindo | 2019-06-03 | 1 | -0/+4 |
| | | | | (GH-13760) | ||||
* | bpo-37115: Support annotations in positional-only arguments (GH-13698) | Pablo Galindo | 2019-05-31 | 1 | -0/+13 |
| | |||||
* | bpo-35798: Add test.support.check_syntax_warning(). (#11895) | Serhiy Storchaka | 2019-02-19 | 1 | -22/+10 |
| | | | | | | | It checks that a SyntaxWarning is raised when compile specified statement, that it is raised only once, that it is converted to a SyntaxError when raised as exception, and that both warning and exception objects have corresponding attributes. | ||||
* | bpo-15248: Emit a compiler warning when missed a comma before tuple or list. ↵ | Serhiy Storchaka | 2019-02-16 | 1 | -0/+87 |
| | | | | (GH-11757) | ||||
* | bpo-35814: Allow same r.h.s. in annotated assignments as in normal ones ↵ | Ivan Levkivskyi | 2019-01-25 | 1 | -0/+9 |
| | | | | | | (GH-11667) | ||||
* | bpo-34850: Emit a warning for "is" and "is not" with a literal. (GH-9642) | Serhiy Storchaka | 2019-01-18 | 1 | -6/+30 |
| | |||||
* | bpo-35029: Replace the SyntaxWarning exception with a SyntaxError. (GH-9999) | Serhiy Storchaka | 2018-10-21 | 1 | -0/+9 |
| | | | | If SyntaxWarning was raised as an exception, it will be replaced with a SyntaxError for better error reporting. | ||||
* | Use assertEqual() instead of assertEquals(). (GH-9721) | Serhiy Storchaka | 2018-10-05 | 1 | -1/+1 |
| | | | Fixes warnings in tests added in bpo-32117 and bpo-34603. | ||||
* | bpo-32117: Allow tuple unpacking in return and yield statements (gh-4509) | David Cuthbert | 2018-09-22 | 1 | -1/+10 |
| | | | | | Iterable unpacking is now allowed without parentheses in yield and return statements, e.g. ``yield 1, 2, 3, *rest``. Thanks to David Cuthbert for the change and jChapman for added tests. | ||||
* | bpo-33305: Improve SyntaxError for invalid numerical literals. (GH-6517) | Serhiy Storchaka | 2018-07-09 | 1 | -0/+24 |
| | |||||
* | bpo-32489: Allow 'continue' in 'finally' clause. (GH-5822) | Serhiy Storchaka | 2018-03-18 | 1 | -0/+53 |
| | |||||
* | bpo-10544: Disallow "yield" in comprehensions and generator expressions. ↵ | Serhiy Storchaka | 2018-02-04 | 1 | -9/+3 |
| | | | | (GH-4564) | ||||
* | bpo-32482: Fix suspicious code in tests for syntax and grammar. (#5086) | Serhiy Storchaka | 2018-01-04 | 1 | -6/+5 |
| | |||||
* | bpo-32478: Add tests for 'break' and 'return' inside 'finally' clause. (#5078) | Serhiy Storchaka | 2018-01-02 | 1 | -0/+74 |
| | |||||
* | bpo-10544: Deprecate "yield" in comprehensions and generator expressions. ↵ | Serhiy Storchaka | 2017-12-01 | 1 | -0/+35 |
| | | | | | | | | | | | | | | (GH-4579) The current behaviour of yield expressions inside comprehensions and generator expressions is essentially an accident of implementation - it arises implicitly from the way the compiler handles yield expressions inside nested functions and generators. Since the current behaviour wasn't deliberately designed, and is inherently confusing, we're deprecating it, with no current plans to reintroduce it. Instead, our advice will be to use a named nested generator definition for cases where this behaviour is desired. | ||||
* | issue #28622: Remove redundant variable annotation test from test_grammar. ↵ | Guido van Rossum | 2016-11-07 | 1 | -3/+0 |
| | | | | Ivan L. | ||||
* | Issue #26182: Raise DeprecationWarning for improper use of async/await keywords | Yury Selivanov | 2016-09-15 | 1 | -12/+0 |
| | |||||
* | Issue #28076: Variable annotations should be mangled for private names. | Guido van Rossum | 2016-09-11 | 1 | -2/+2 |
| | | | | By Ivan Levkivskyi. | ||||
* | Issue #26331: Implement the parsing part of PEP 515. | Brett Cannon | 2016-09-09 | 1 | -0/+89 |
| | | | | Thanks to Georg Brandl for the patch. | ||||
* | Issue #27985: Implement PEP 526 -- Syntax for Variable Annotations. | Yury Selivanov | 2016-09-09 | 1 | -0/+178 |
| | | | | Patch by Ivan Levkivskyi. | ||||
* | Issue #27095: Simplified MAKE_FUNCTION and removed MAKE_CLOSURE opcodes. | Serhiy Storchaka | 2016-06-12 | 1 | -1/+1 |
| | | | | Patch by Demur Rumed. | ||||
* | Merge 3.5 (issue #27243) | Yury Selivanov | 2016-06-09 | 1 | -1/+1 |
|\ | |||||
| * | Issue #27243: Fix __aiter__ protocol | Yury Selivanov | 2016-06-09 | 1 | -1/+1 |
| | | |||||
* | | Merge 3.5 | Victor Stinner | 2016-04-12 | 1 | -1/+1 |
|\ \ | |/ | |||||
| * | Issue #26647: Fix typo in test_grammar | Victor Stinner | 2016-04-12 | 1 | -1/+1 |
| | | | | | | | | Patch written by Demur Rumed. | ||||
* | | compiler: don't emit SyntaxWarning on const stmt | Victor Stinner | 2016-02-08 | 1 | -5/+1 |
| | | | | | | | | | | Issue #26204: the compiler doesn't emit SyntaxWarning warnings anymore when constant statements are ignored. | ||||
* | | compiler now ignores constant statements | Victor Stinner | 2016-02-08 | 1 | -1/+5 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The compile ignores constant statements and emit a SyntaxWarning warning. Don't emit the warning for string statement because triple quoted string is a common syntax for multiline comments. Don't emit the warning on ellipis neither: 'def f(): ...' is a legit syntax for abstract functions. Changes: * test_ast: ignore SyntaxWarning when compiling test statements. Modify test_load_const() to use assignment expressions rather than constant expression. * test_code: add more kinds of constant statements, ignore SyntaxWarning when testing that the compiler removes constant statements. * test_grammar: ignore SyntaxWarning on the statement "1" | ||||
* | | Issue #9232: Support trailing commas in function declarations. | Robert Collins | 2015-08-11 | 1 | -0/+38 |
|/ | | | | | | For example, "def f(*, a = 3,): pass" is now legal. Patch from Mark Dickinson. | ||||
* | Issue #24791: Fix grammar regression for call syntax: 'g(*a or b)'. | Yury Selivanov | 2015-08-05 | 1 | -0/+2 |
| | |||||
* | Issue #23182: Merge with 3.4 | Zachary Ware | 2015-08-02 | 1 | -12/+12 |
|\ | |||||
| * | Issue #23182: PEP8-ify the annotation grammar tests. Patch by Ian Lee. | Zachary Ware | 2015-08-02 | 1 | -12/+12 |
| | | |||||
* | | Issue #24687: Plug refleak on SyntaxError in function parameters annotations. | Yury Selivanov | 2015-07-23 | 1 | -1/+2 |
| | | |||||
* | | Issue #24619: New approach for tokenizing async/await. | Yury Selivanov | 2015-07-22 | 1 | -4/+1 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit fixes how one-line async-defs and defs are tracked by tokenizer. It allows to correctly parse invalid code such as: >>> async def f(): ... def g(): pass ... async = 10 and valid code such as: >>> async def f(): ... async def g(): pass ... await z As a consequence, is is now possible to have one-line 'async def foo(): await ..' functions: >>> async def foo(): return await bar() | ||||
* | | allow test node after ** in calls (closes #24176) | Benjamin Peterson | 2015-05-16 | 1 | -0/+1 |
| | | |||||
* | | PEP 0492 -- Coroutines with async and await syntax. Issue #24017. | Yury Selivanov | 2015-05-12 | 1 | -0/+87 |
| | | |||||
* | | PEP 448: additional unpacking generalizations (closes #2292) | Benjamin Peterson | 2015-05-06 | 1 | -1/+5 |
| | | | | | | | | Patch by Neil Girdhar. | ||||
* | | Issue #21741: Update 147 test modules to use test discovery. | Zachary Ware | 2015-04-13 | 1 | -5/+2 |
| | | | | | | | | | | | | | | I have compared output between pre- and post-patch runs of these tests to make sure there's nothing missing and nothing broken, on both Windows and Linux. The only differences I found were actually tests that were previously *not* run. | ||||
* | | Merge issue #21669 from 3.4 | Nick Coghlan | 2014-06-16 | 1 | -0/+25 |
|\ \ | |/ | |||||
| * | Issue #21669: Special case print & exec syntax errors | Nick Coghlan | 2014-06-16 | 1 | -0/+25 |
| | | |||||
* | | merge 3.4 (#21642) | Benjamin Peterson | 2014-06-07 | 1 | -0/+6 |
|\ \ | |/ | |||||
| * | allow the keyword else immediately after (no space) an integer (closes #21642) | Benjamin Peterson | 2014-06-07 | 1 | -0/+6 |
| | | |||||
* | | PEP 465: a dedicated infix operator for matrix multiplication (closes #21176) | Benjamin Peterson | 2014-04-10 | 1 | -0/+14 |
|/ | |||||
* | use assertEqual instead of the deprecated assertEquals (closes #20877) | Benjamin Peterson | 2014-03-10 | 1 | -2/+2 |
| | |||||
* | Mangle __parameters in __annotations__ dict properly. Issue #20625. | Yury Selivanov | 2014-02-18 | 1 | -0/+7 |
| | |||||
* | Implement PEP 380 - 'yield from' (closes #11682) | Nick Coghlan | 2012-01-13 | 1 | -0/+32 |
| | |||||
* | #8414: merge with 3.2. | Ezio Melotti | 2011-12-02 | 1 | -2/+24 |
|\ | |||||
| * | #8414: add more tests for "assert". Initial patch by Gregory Nofi. | Ezio Melotti | 2011-12-02 | 1 | -2/+24 |
| | | |||||
* | | don't restrict unexpected EOF errors to the first line (closes #12216) | Benjamin Peterson | 2011-05-30 | 1 | -0/+7 |
| | | |||||
* | | use better naming scheme | Benjamin Peterson | 2011-05-30 | 1 | -42/+42 |
|/ |