cpython.git - https://github.com/python/cpython.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add another f-string comment test, to make sure # are being caught in the ↵	Eric V. Smith	2016-09-11	1	-0/+2
\| \| \| \|	right place.
*	Make an f-string error message more exact and consistent.	Eric V. Smith	2016-09-11	1	-1/+2
\|
*	Issue 27948: Allow backslashes in the literal string portion of f-strings, ↵	Eric V. Smith	2016-09-10	1	-46/+86
\| \| \| \|	but not in the expressions. Also, require expressions to begin and end with literal curly braces.
*	Closes issue 27921: Disallow backslashes anywhere in f-strings. This is a ↵	Eric V. Smith	2016-09-03	1	-91/+51
\| \| \| \|	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.
*	Issue #27626: Further spelling fixes for 3.6	Martin Panter	2016-07-28	1	-1/+1
\|
*	Fix issue 26287: While handling FORMAT_VALUE opcode, the top of stack was ↵	Eric V. Smith	2016-02-05	1	-0/+11
\| \| \| \|	being corrupted if an error occurred in PyObject_Format().
*	f-strings: More tests for empty expressions along with missing closing braces.	Eric V. Smith	2015-09-23	1	-0/+7
\|
*	Added more f-string test for empty expressions.	Eric V. Smith	2015-09-23	1	-0/+3
\|
*	Move f-string compilation of the expression earlier, before the conversion ↵	Eric V. Smith	2015-09-23	1	-0/+9
\| \| \| \|	character and format_spec are checked. This allows for error messages that more closely match what a user would expect.
*	Issue #24965: Implement PEP 498 "Literal String Interpolation". ↵	Eric V. Smith	2015-09-19	1	-0/+715
	Documentation is still needed, I'll open an issue for that.