From 23217307577f1d351ad8831c0692d19fc9fda886 Mon Sep 17 00:00:00 2001 From: Serhiy Storchaka Date: Wed, 9 May 2018 11:10:55 +0300 Subject: [PATCH] [2.7] bpo-13525: Fix incorrect encoding name in the tutorial example. (GH-6738). (cherry picked from commit ddb6215a55b0218b621d5cb755e9dfac8dab231a) Co-authored-by: Serhiy Storchaka --- Doc/tutorial/interpreter.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/tutorial/interpreter.rst b/Doc/tutorial/interpreter.rst index 6c8609fabaeb52..b727be00ab8aa3 100644 --- a/Doc/tutorial/interpreter.rst +++ b/Doc/tutorial/interpreter.rst @@ -137,12 +137,12 @@ where *encoding* is one of the valid :mod:`codecs` supported by Python. For example, to declare that Windows-1252 encoding is to be used, the first line of your source code file should be:: - # -*- coding: cp-1252 -*- + # -*- coding: cp1252 -*- One exception to the *first line* rule is when the source code starts with a :ref:`UNIX "shebang" line `. In this case, the encoding declaration should be added as the second line of the file. For example:: #!/usr/bin/env python - # -*- coding: cp-1252 -*- + # -*- coding: cp1252 -*-