Python～SyntaxError: Non-ASCII character “\xe6” in file 。。。PEP 263

PEP 263 – Defining Python Source Code Encodings

---

SyntaxError: Non-ASCII character ‘\xe6’ in file /home/geek/PycharmProjects/untitled/requests_demo.py on line 18, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details

PEP 263 – Defining Python Source Code Encodings

In Python 2.1, Unicode literals can only be written using the Latin-1 based encoding “unicode-escape”. This makes the programming environment rather unfriendly to Python users who live and work in non-Latin-1 locales such as many of the Asian countries. Programmers can write their 8-bit strings using the favorite encoding, but are bound to the “unicode-escape” encoding for Unicode literals.

Python 2.1 版本时，Unicode 文本只能使用基于拉丁语 1 的编码“Unicode-escape” 来编写。这使得编程环境对生活和工作在非拉丁语1语言环境（如许多亚洲国家）中的 Python 用户相当不友好。程序员可以使用最喜欢的编码来编写 8 bit 字符，但必须是 unicode-escape 字符集的编码形式。

Python 定义编码。

• Python 默认使用 ASCII 码。

Python will default to ASCII as standard encoding if no other encoding hints are given.

To define a source code encoding, a magic comment must be placed into the source files either as first or second line in the file, such as:

• 使用“魔法注释”来定义编码。

ta 以 # 开头（注释），但 ta 可以告诉 Python 执行器以什么编码去执行该 Python 程序。

# coding=<encoding name>

or (using formats recognized by popular editors):

#!/usr/bin/python
# -*- coding: <encoding name> -*-

or:

#!/usr/bin/python
# vim: set fileencoding=<encoding name> :

More precisely, the first or second line must match the following regular expression:

^[ \t\f]*#.*?coding[:=][ \t]*([-_.a-zA-Z0-9]+)

The first group of this expression is then interpreted as encoding name. If the encoding is unknown to Python, an error is raised during compilation. There must not be any Python statement on the line that contains the encoding declaration. If the first line matches the second line is ignored.

To aid with platforms such as Windows, which add Unicode BOM marks to the beginning of Unicode files, the UTF-8 signature \xef\xbb\xbf will be interpreted as ‘utf-8’ encoding as well (even if no magic encoding comment is given).

If a source file uses both the UTF-8 BOM mark signature and a magic encoding comment, the only allowed encoding for the comment is ‘utf-8’. Any other encoding will cause an error.