blocks|key|201644|text|在需要在代码中使用非ascii字符的地方，例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|201645|ă+|code-block|syntax|javascript|201646|翻译员会抱怨他不理解那个字符。|201647|通常在定义常量时会发生这种情况。|201648|示例:添加到x.py|201649|print+'ă'|201650|然后启动python控制台|201651|import+x
Traceback+(most+recent+call+last):
++File+"<stdin>",+line+1,+in+<module>
++File+"x.py",+line+1
+SyntaxError:+Non-ASCII+character+'\xc4'+in+file+x.py+on+line+1,+
+++but+no+encoding+declared;
+++see+http://www.python.org/peps/pep-0263.html+for+details|201652|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

wherever you need to use in your code chars that aren't from ascii, like:

<pre><code>ă 
</code></pre>

interpreter will complain that he doesn't understand that char.

Usually this happens when you define constants.

Example:
Add into x.py

<pre><code>print 'ă'
</code></pre>

then start a python console

<pre><code>import x
Traceback (most recent call last):
 File "&lt;stdin&gt;", line 1, in &lt;module&gt;
 File "x.py", line 1
 SyntaxError: Non-ASCII character '\xc4' in file x.py on line 1, 
 but no encoding declared;
 see http://www.python.org/peps/pep-0263.html for details
</code></pre>

blocks|key|201709|text|当您使用非ascii字符时。例如，当我用挪威语注释我的源码时，如果在.py中出现了charachters，它就会报错，而不是“编译”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|201710|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

When you use non-ascii characters. For instance when I comment my source in norwegian if charachters ØÆÅ occur in the .py it will complain and not "compile".

blocks|key|420109|text|每当读取或写入文本时，编码都会起作用。一直都是。python解释器必须将文件作为文本读取，才能理解它。当您只使用ASCII范围内的字符时，您可以不必处理编码的唯一情况。在这种情况下，解释器几乎可以使用世界上的任何编码，并且可以正确使用，因为几乎所有的编码都将这些字符编码为相同的字节。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|420110|你不应该仅仅因为你的文件中有ascii以外的字符就使用coding:+utf-8，它甚至是有害的。它是python解释器的一个提示，告诉它您的文件采用的是什么编码。除非您配置了文本编辑器，否则文本编辑器很可能不会将您的文件保存为utf-8格式。所以现在你给python解释器的提示是错误的。|offset|length|style|CODE|420111|因此，当您的文件以utf-8编码时，您应该使用它。如果它是用windows-1252编码的，你应该使用coding:+windows-1252等等。|420112|entityMap^0|0|R|D|0|1F|K|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

Whenever text is read or written, encodings come in play. Always. A python interpreter has to read your file as text, to understand it. The only situation where you could get away without having to deal with encodings is when you only use characters in the ASCII range. The interpreter can in this case use virtually any encoding in the world, and get it right because almost all encodings encode these characters to same bytes.

You should not use <code>coding: utf-8</code> just because you have characters beyond ascii in your file, it can even be harmful. It is a hint for the python interpreter, to tell it what encoding your file is in. Unless you have configured your text editor, the text editor will most likely not save your files in utf-8. So now the hint you gave to the python interpreter, is wrong.

So you should use it when your file is encoded in utf-8. If it's encoded in windows-1252, you should use <code>coding: windows-1252</code> and so on.

blocks|key|201807|text|始终使用UTF-8，并确保您的编辑器也使用UTF-8。如果使用Python+27，请像这样启动Python脚本：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|201808|#!/usr/bin/env+python
#+-*-+coding:+utf-8+-*-
from+__future__+import+unicode_literals|code-block|syntax|javascript|201809|这是Nick+Johnson关于Python和UTF-8的一篇很好的博客文章：|201810|http://blog.notdot.net/2010/07/Getting-unicode-right-in-Python顺便说一句，这篇文章是在他可以使用之前写的：|offset|length|201811|from+__future__+import+unicode_literals|201812|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.notdot.net/2010/07/Getting-unicode-right-in-Python^0|0|0|0|0|1Q|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Z|8|@]|9|@$K|10|L|11|1|12]]|A|$]]|$1|M|3|N|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

Always use UTF-8 and make sure your editor also uses UTF-8.
Start your Python script like this if you use Python 27:

<pre><code>#!/usr/bin/env python
# -*- coding: utf-8 -*-
from __future__ import unicode_literals
</code></pre>

This is a good blog post from Nick Johnson about Python and UTF-8:

<a href="http://blog.notdot.net/2010/07/Getting-unicode-right-in-Python" rel="noreferrer">http://blog.notdot.net/2010/07/Getting-unicode-right-in-Python</a>
By the way, this post was written before he could use:

<pre><code>from __future__ import unicode_literals
</code></pre>

Some source files, from downloaded code, have the following header

<pre><code># -*- coding: utf-8 -*-
</code></pre>

I have an idea what utf-8 encoding is but why would it be needed as a header in a python source file?

When to use utf8 as a header in py files

解释器

Python

一些来自下载代码的源文件具有以下标头# -*- coding: utf-8 -*-我知道什么是utf-8编码，但是为什么要把它作为python源文件的头文件呢？

问何时在py文件中使用utf8作为头文件
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问何时在py文件中使用utf8作为头文件EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问何时在py文件中使用utf8作为头文件
EN