[issue30955] \\N in f-string causes next { to be literal if not escaped

[Ned Deily]

Ned Deily added the comment:

Thanks for the report.  This problem has been fixed in Python 3.6.2 which was 
just released.  I believe it was fixed by the changes for Issue29104.

--
nosy: +ned.deily
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30955] \\N in f-string causes next { to be literal if not escaped

[Mital Ashok]

New submission from Mital Ashok:

Take this format python code:

import unicodedata
c = chr(0x012345)

To print that character as a string literal, you would expect to do:

print(f"'\\N{{{unicodedata.name(c)}}}'")

Which should print a literal quote (`'`), a backwards slash (`\\` -> `\`), an 
`N`, and the two `{{` should escape and print `{`, followed by the f-expression 
`unicodedata.name(c)`, then the `}}` would print one `}`, and then another 
literal quote (`'`).

However, this raises a `SyntaxError: f-string: single '}' is not allowed`. The 
way to do this without a syntax error is like so:

print(f"'\\N{{unicodedata.name(c)}}}'")

Which prints the expected:

'\N{CUNEIFORM SIGN URU TIMES KI}'

The shortest way to reproduce this is:

f'\\N{'

Which works, and:

f'\\N{{'

which raises an error, even though the first one should raise an error 
(`SyntaxError: f-string: expecting '}'`).

--
messages: 298563
nosy: Mital Ashok
priority: normal
severity: normal
status: open
title: \\N in f-string causes next { to be literal if not escaped
versions: Python 3.6, Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com