Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / python / cpython3 / c615db608dbb36a5d10188f7d265dcec7bfcc3cf / Lib / test / test_fstring.py
  1. 4c5b6ba [3.8] bpo-32912: Revert SyntaxWarning on invalid escape sequences (GH-15142) by Serhiy Storchaka · 5 years ago
  2. 24b5b36 [3.8] Fix typos in docs, comments and test assert messages (GH-14872). (#14900) by Kyle Stanley · 5 years ago
  3. 6f6ff8a bpo-37050: Remove expr_text from FormattedValue ast node, use Constant node instead (GH-13597) by Eric V. Smith · 5 years ago
  4. 26f55c2 bpo-36817: Do not decrement reference for expr_text on fstring = parsing failure (GH-13256) by Pablo Galindo · 5 years ago
  5. 9a4135e bpo-36817: Add f-string debugging using '='. (GH-13123) by Eric V. Smith · 5 years ago
  6. 995d9b9 bpo-16806: Fix `lineno` and `col_offset` for multi-line string tokens (GH-10021) by Anthony Sottile · 6 years ago
  7. 58159ef bpo-35494: Improve syntax error messages for unbalanced parentheses in f-string. (GH-11161) by Serhiy Storchaka · 6 years ago
  8. 94cf308 bpo-33306: Improve SyntaxError messages for unbalanced parentheses. (GH-6516) by Serhiy Storchaka · 6 years ago
  9. 6543912 bpo-32912: Replace a DeprecationWarning with a SyntaxWarning (GH-9652) by Serhiy Storchaka · 6 years ago
  10. 3f22811 bpo-32892: Use ast.Constant instead of specific constant AST types. (GH-9445) by Serhiy Storchaka · 6 years ago
  11. e7c566c bpo-30465: Fix lineno and col_offset in fstring AST nodes (#1800) by Łukasz Langa · 7 years ago
  12. 11e97f2 bpo-30682: Removed a too-strict assertion that failed for certain f-strings. (#2232) by ericvsmith · 7 years ago
  13. 2e9cd58 bpo-30529: Fix errors for invalid whitespaces in f-string subexpressions. (#1888) by Serhiy Storchaka · 7 years ago
  14. 0cd7a3f bpo-29104: Fixed parsing backslashes in f-strings. (#490) by Serhiy Storchaka · 7 years ago
  15. 4cc30ae Issue #28739: f-string expressions no longer accepted as docstrings and by Serhiy Storchaka · 8 years ago
  16. 9b88fdf Fixed issue #28633: segfault when concatenating bytes literal and f-string. by Eric V. Smith · 8 years ago
  17. 1c92a76 Update test_no_escapes_for_braces to clarify behavior with a docstring and expressions that clearly are not evaluated. by Jason R. Coombs · 8 years ago
  18. da25abf7 Additionally show that a backslash-escaped opening brace is treated as a literal and thus triggers the single closing brace error, clarifying #28590. by Jason R. Coombs · 8 years ago
  19. 45cab8c Add an additional test with a newline, one that's very similar to test_parens_in_expressions, but because the newline is not a literal newline, but a backslash en, this error is triggered. by Jason R. Coombs · 8 years ago
  20. 13c8f32 Update the f-string test broken in issue #28385. by Serhiy Storchaka · 8 years ago
  21. 35a24c5 Add another f-string comment test, to make sure # are being caught in the right place. by Eric V. Smith · 8 years ago
  22. 09835dc Make an f-string error message more exact and consistent. by Eric V. Smith · 8 years ago
  23. 451d0e3 Issue 27948: Allow backslashes in the literal string portion of f-strings, but not in the expressions. Also, require expressions to begin and end with literal curly braces. by Eric V. Smith · 8 years ago
  24. 6a4efce Closes issue 27921: Disallow backslashes anywhere in f-strings. This is a temporary restriction. In 3.6 beta 2, the plan is to again allow backslashes in the string parts of f-strings, but disallow them in the expression parts. by Eric V. Smith · 8 years ago
  25. 263893c Issue #27626: Further spelling fixes for 3.6 by Martin Panter · 8 years ago
  26. 135d5f4 Fix issue 26287: While handling FORMAT_VALUE opcode, the top of stack was being corrupted if an error occurred in PyObject_Format(). by Eric V. Smith · 8 years ago
  27. b2080f6 f-strings: More tests for empty expressions along with missing closing braces. by Eric V. Smith · 9 years ago
  28. 548c4d3 Added more f-string test for empty expressions. by Eric V. Smith · 9 years ago
  29. 1d44c41 Move f-string compilation of the expression earlier, before the conversion character and format_spec are checked. This allows for error messages that more closely match what a user would expect. by Eric V. Smith · 9 years ago
  30. 235a6f0 Issue #24965: Implement PEP 498 "Literal String Interpolation". Documentation is still needed, I'll open an issue for that. by Eric V. Smith · 9 years ago