commit 2eca5b465f7404cc8484457b7966f828f434ec20
author Serhiy Storchaka <storchaka@gmail.com> Fri Jun 16 16:29:42 2017 +0300
committer ericvsmith <ericvsmith@users.noreply.github.com> Fri Jun 16 09:29:42 2017 -0400
tree 24eb2215c217bd8669b0f5da5e098f3ebf0cd3be
parent a0ccc54e6dffacf9e7c06f2a3e9056d2d35d21eb

[3.6] bpo-30682: Removed a too-strict assertion that failed for certain f-strings. (GH-2232) (#2242)

This caused a segfault on eval("f'\\\n'") and eval("f'\\\r'") in debug build..
(cherry picked from commit 11e97f2f80bf65cc828c127eafc95229df35d403)

Lib/test/test_fstring.py

diff --git a/Lib/test/test_fstring.py b/Lib/test/test_fstring.py
index b398704..3d762b5 100644
--- a/Lib/test/test_fstring.py
+++ b/Lib/test/test_fstring.py
@@ -780,5 +780,11 @@
         self.assertEqual(f'{d["foo"]}', 'bar')
         self.assertEqual(f"{d['foo']}", 'bar')
 
+    def test_backslash_char(self):
+        # Check eval of a backslash followed by a control char.
+        # See bpo-30682: this used to raise an assert in pydebug mode.
+        self.assertEqual(eval('f"\\\n"'), '')
+        self.assertEqual(eval('f"\\\r"'), '')
+
 if __name__ == '__main__':
     unittest.main()