From: Serhiy Storchaka <storchaka@gmail.com>
Date: Wed, 9 May 2018 08:10:55 +0000 (+0300)
Subject: bpo-13525: Fix incorrect encoding name in the tutorial example. (GH-6738)
X-Git-Tag: v3.8.0a1~1879
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ddb6215a55b0218b621d5cb755e9dfac8dab231a;p=python

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

diff --git a/Doc/tutorial/interpreter.rst b/Doc/tutorial/interpreter.rst
index 3d57020dab..6cdc6c8419 100644
--- a/Doc/tutorial/interpreter.rst
+++ b/Doc/tutorial/interpreter.rst
@@ -148,14 +148,14 @@ 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 python3
-   # -*- coding: cp-1252 -*-
+   # -*- coding: cp1252 -*-
 
 .. rubric:: Footnotes