From: Serhiy Storchaka <storchaka@gmail.com>
Date: Wed, 9 May 2018 09:35:28 +0000 (+0300)
Subject: [2.7] bpo-13525: Fix incorrect encoding name in the tutorial example. (GH-6738).... 
X-Git-Tag: v2.7.16rc1~306
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d7e783b17feaedbe0f5b30467cb7f43cefadf904;p=thirdparty%2FPython%2Fcpython.git

[2.7] bpo-13525: Fix incorrect encoding name in the tutorial example. (GH-6738). (GH-6744)

(cherry picked from commit ddb6215a55b0218b621d5cb755e9dfac8dab231a)
---

diff --git a/Doc/tutorial/interpreter.rst b/Doc/tutorial/interpreter.rst
index 6c8609fabaeb..b727be00ab8a 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 <tut-scripts>`.  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 -*-