[issue27921] f-strings: do not allow backslashes

Eric V. Smith added the comment: Issue 28002 tracks the problem with Tools/parser/unparse.py. -- ___ Python tracker ___

[issue27921] f-strings: do not allow backslashes

Eric V. Smith added the comment: The problem with test_unparse is that: f'''{"'"}''' becomes: f'{"\'"}' when it's run through Tools/parser/unparse.py. I'll open another issue for this. -- ___ Python tracker

[issue27921] f-strings: do not allow backslashes

Roundup Robot added the comment: New changeset df5b6d1c7ea8 by Benjamin Peterson in branch 'default': fix skipping #27921 for windows https://hg.python.org/cpython/rev/df5b6d1c7ea8 -- ___ Python tracker

[issue27921] f-strings: do not allow backslashes

Martin Panter added the comment: I haven’t looked, but my guess at why test_unparse could fail would be trying to generate code for an f-string with control characters in. Maybe it is taking stuff like f'''{x} {y} ''' and generating f'{x}\n{y}\n' -- nosy: +martin.panter

[issue27921] f-strings: do not allow backslashes

Roundup Robot added the comment: New changeset fd4e4fa75260 by Eric V. Smith in branch 'default': Issue 27921: Remove backslash from another f-string. I'll revert this change before beta 2. I also need to look in to why test_tools/test_unparse fails with the files that are now being skipped.

[issue27921] f-strings: do not allow backslashes

Roundup Robot added the comment: New changeset 80eb6eb57537 by Eric V. Smith in branch 'default': Issue 27921: Remove backslash from another f-string. I'll revert this change before beta 2. https://hg.python.org/cpython/rev/80eb6eb57537 -- ___

[issue27921] f-strings: do not allow backslashes

Roundup Robot added the comment: New changeset 899ee1e68a8d by Eric V. Smith in branch 'default': Issue 27921: Remove backslash from another f-string. https://hg.python.org/cpython/rev/899ee1e68a8d -- ___ Python tracker

[issue27921] f-strings: do not allow backslashes

Eric V. Smith added the comment: See issue 27948 for adding backslashes back in to the string parts of an f-string. -- ___ Python tracker ___

[issue27921] f-strings: do not allow backslashes

Roundup Robot added the comment: New changeset d7ce127b5c0f by Eric V. Smith in branch 'default': 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

[issue27921] f-strings: do not allow backslashes

Eric V. Smith added the comment: > This looks a little ugly. True. My goal is to get the simplest possible thing working now, and then before beta 2 fix it so that backslashes again work in the text portions of an f-string. After that, I'll fix this particular piece of code (and the others,

[issue27921] f-strings: do not allow backslashes

Serhiy Storchaka added the comment: > -result.append(f' [Previous line repeated {count-3} more > times]\n') > +result.append(f' [Previous line repeated {count-3} more > times]''\n') This looks a little ugly. -- nosy: +serhiy.storchaka

[issue27921] f-strings: do not allow backslashes

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list

[issue27921] f-strings: do not allow backslashes

Changes by Eric V. Smith : -- keywords: +patch Added file: http://bugs.python.org/file44311/27921.patch ___ Python tracker ___

[issue27921] f-strings: do not allow backslashes

Changes by Eric V. Smith : -- stage: -> patch review ___ Python tracker ___ ___

[issue27921] f-strings: do not allow backslashes

New submission from Eric V. Smith: See https://mail.python.org/pipermail/python-dev/2016-August/145979.html for details. PEP 498 is going to be changed to disallow backslashes inside braces (the expression portions of an f-string). However, I can't get that change done in time for 3.6 beta