Eric V. Smith
|
09835dcdbb
|
Make an f-string error message more exact and consistent.
|
2016-09-11 18:58:20 -04:00 |
|
Eric V. Smith
|
451d0e38fc
|
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.
|
2016-09-09 21:56:20 -04:00 |
|
Eric V. Smith
|
6a4efce7a5
|
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.
|
2016-09-03 09:18:34 -04:00 |
|
Martin Panter
|
263893c261
|
Issue #27626: Further spelling fixes for 3.6
|
2016-07-28 01:25:31 +00:00 |
|
Eric V. Smith
|
135d5f49f6
|
Fix issue 26287: While handling FORMAT_VALUE opcode, the top of stack was being corrupted if an error occurred in PyObject_Format().
|
2016-02-05 18:23:08 -05:00 |
|
Eric V. Smith
|
b2080f6554
|
f-strings: More tests for empty expressions along with missing closing braces.
|
2015-09-23 10:24:43 -04:00 |
|
Eric V. Smith
|
548c4d3178
|
Added more f-string test for empty expressions.
|
2015-09-23 08:00:01 -04:00 |
|
Eric V. Smith
|
1d44c41b0c
|
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.
|
2015-09-23 07:49:00 -04:00 |
|
Eric V. Smith
|
235a6f0984
|
Issue #24965: Implement PEP 498 "Literal String Interpolation". Documentation is still needed, I'll open an issue for that.
|
2015-09-19 14:51:32 -04:00 |
|