Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add spaces around the ":=" operator in ast_unparse.c (GH-19568) | Hakan Çelik | 2020-04-18 | 1 | -1/+1 |
| | |||||
* | bpo-39522: Use _PyUnicodeWriter_WriteStr instead of PyUnicode_AS_DATA (GH-19523) | Batuhan Taşkaya | 2020-04-14 | 1 | -2/+4 |
| | |||||
* | bpo-395222: Correctly unparse unicode prefix in ast_unparse.c (GH-19512) | Batuhan Taşkaya | 2020-04-14 | 1 | -0/+2 |
| | |||||
* | bpo-32894: Support unparsing of infinity numbers in ast_unparser.c (GH-17426) | Batuhan Taşkaya | 2020-04-14 | 1 | -5/+53 |
| | |||||
* | bpo-34822: Simplify AST for subscription. (GH-9605) | Serhiy Storchaka | 2020-03-10 | 1 | -40/+11 |
| | | | | | | | | | * Remove the slice type. * Make Slice a kind of the expr type instead of the slice type. * Replace ExtSlice(slices) with Tuple(slices, Load()). * Replace Index(value) with a value itself. All non-terminal nodes in AST for expressions are now of the expr type. | ||||
* | closes bpo-39898: Remove unused arg from append_formattedvalue. (GH-18840) | Andy Lester | 2020-03-08 | 1 | -4/+4 |
| | |||||
* | bpo-39520: Fix un-parsing of ext slices with no dimensions (GH-18304) | Batuhan Taşkaya | 2020-03-01 | 1 | -0/+1 |
| | |||||
* | bpo-37050: Remove expr_text from FormattedValue ast node, use Constant node ↵ | Eric V. Smith | 2019-05-27 | 1 | -5/+0 |
| | | | | | instead (GH-13597) When using the "=" debug functionality of f-strings, use another Constant node (or a merged constant node) instead of adding expr_text to the FormattedValue node. | ||||
* | bpo-36961: Handle positional-only arguments in uparse.c (GH-13412) | Pablo Galindo | 2019-05-18 | 1 | -6/+16 |
| | |||||
* | Add support for PEP572 in ast_unparse.c (GH-13337) | Batuhan Taşkaya | 2019-05-18 | 1 | -0/+13 |
| | |||||
* | bpo-36817: Add f-string debugging using '='. (GH-13123) | Eric V. Smith | 2019-05-08 | 1 | -0/+5 |
| | | | If a "=" is specified a the end of an f-string expression, the f-string will evaluate to the text of the expression, followed by '=', followed by the repr of the value of the expression. | ||||
* | bpo-34854: Fix compiling string annotations containing lambdas. (GH-9645) | Serhiy Storchaka | 2018-09-30 | 1 | -4/+7 |
| | | | | | | | | | | * Compiling a string annotation containing a lambda with keyword-only argument without default value caused a crash. * Remove the final "*" (it is incorrect syntax) in the representation of lambda without *args and keyword-only arguments when compile from AST. * Improve the representation of lambda without arguments. | ||||
* | bpo-32892: Use ast.Constant instead of specific constant AST types. (GH-9445) | Serhiy Storchaka | 2018-09-27 | 1 | -17/+7 |
| | |||||
* | bpo-33475: Fix and improve converting annotations to strings. (GH-6774) | Serhiy Storchaka | 2018-05-16 | 1 | -536/+290 |
| | |||||
* | bpo-32711: Fix warnings for Python/ast_unparse.c (#5426) | Stéphane Wirtel | 2018-02-01 | 1 | -3/+7 |
| | | | * bpo-32711: Fix warnings for Python/ast_unparse.c | ||||
* | String annotations [PEP 563] (#4390) | Guido van Rossum | 2018-01-26 | 1 | -0/+1163 |
* Document `from __future__ import annotations` * Provide plumbing and tests for `from __future__ import annotations` * Implement unparsing the AST back to string form This is required for PEP 563 and as such only implements a part of the unparsing process that covers expressions. |