[issue28597] f-string behavior is conflicting with its documentation

Eric V. Smith added the comment: This is a duplicate of issue 28590. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> fstring's '{' from escape sequences does not start an expression ___ Python tracker

[issue28597] f-string behavior is conflicting with its documentation

Changes by Serhiy Storchaka : -- assignee: -> docs@python components: +Documentation -Interpreter Core nosy: +docs@python, eric.smith type: -> behavior versions: +Python 3.7 ___ Python tracker ___

[issue28597] f-string behavior is conflicting with its documentation

New submission from Fabio Zadrozny: The file: /Doc/reference/lexical_analysis.rst says that things as: f"abc {a[\"x\"]} def" # workaround: escape the inner quotes f"newline: {ord('\\n')}" # workaround: double escaping fr"newline: {ord('\n')}" # workaround: raw outer string are accepted in f