由于我还没有看到Python 2.7的完整答案，我将概述两个重要步骤和一个非常有用的可选步骤。

You need a font with Unicode support. Windows comes with Lucida Console which may be selected by right-clicking the title bar of command prompt and clicking the Defaults option. This also gives access to colours. Note that you can also change settings for command windows invoked in certain ways (e.g, open here, Visual Studio) by choosing Properties instead. You need to set the code page to cp65001, which appears to be Microsoft's attempt to offer UTF-7 and UTF-8 support to command prompt. Do this by running chcp 65001 in command prompt. Once set, it remains this way until the window is closed. You'll need to redo this every time you launch cmd.exe.

要获得更永久的解决方案，请参考超级用户上的答案。简而言之，在HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor中使用regedit创建一个REG_SZ (String)条目，并将其命名为AutoRun。将其值修改为chcp 65001。如果不想看到命令的输出消息，请使用@chcp 65001>nul。

有些程序在与这种编码进行交互时遇到麻烦，MinGW就是一个显著的例子，它在编译时出现无意义的错误消息而失败。尽管如此，这工作得非常好，并且不会对大多数程序造成错误。

Try:

chcp 65001

这会将代码页更改为UTF-8。此外，还需要使用Lucida控制台字体。

我的背景:我在控制台中使用Unicode输入/输出已经很多年了(并且每天都这么做。此外，我还为这项任务开发了支持工具)。只要你了解以下事实/限制，问题就很少:

CMD and “console” are unrelated factors. CMD.exe is a just one of programs which are ready to “work inside” a console (“console applications”). AFAIK, CMD has perfect support for Unicode; you can enter/output all Unicode chars when any codepage is active. Windows’ console has A LOT of support for Unicode — but it is not perfect (just “good enough”; see below). chcp 65001 is very dangerous. Unless a program was specially designed to work around defects in the Windows’ API (or uses a C runtime library which has these workarounds), it would not work reliably. Win8 fixes ½ of these problems with cp65001, but the rest is still applicable to Win10. I work in cp1252. As I already said: To input/output Unicode in a console, one does not need to set the codepage.

细节

To read/write Unicode to a console, an application (or its C runtime library) should be smart enough to use not File-I/O API, but Console-I/O API. (For an example, see how Python does it.) Likewise, to read Unicode command-line arguments, an application (or its C runtime library) should be smart enough to use the corresponding API. Console font rendering supports only Unicode characters in BMP (in other words: below U+10000). Only simple text rendering is supported (so European — and some East Asian — languages should work fine — as far as one uses precomposed forms). [There is a minor fine print here for East Asian and for characters U+0000, U+0001, U+30FB.]

实际考虑

The defaults on Window are not very helpful. For best experience, one should tune up 3 pieces of configuration: For output: a comprehensive console font. For best results, I recommend my builds. (The installation instructions are present there — and also listed in other answers on this page.) For input: a capable keyboard layout. For best results, I recommend my layouts. For input: allow HEX input of Unicode. One more gotcha with “Pasting” into a console application (very technical): HEX input delivers a character on KeyUp of Alt; all the other ways to deliver a character happen on KeyDown; so many applications are not ready to see a character on KeyUp. (Only applicable to applications using Console-I/O API.) Conclusion: many application would not react on HEX input events. Moreover, what happens with a “Pasted” character depends on the current keyboard layout: if the character can be typed without using prefix keys (but with arbitrary complicated combination of modifiers, as in Ctrl-Alt-AltGr-Kana-Shift-Gray*) then it is delivered on an emulated keypress. This is what any application expects — so pasting anything which contains only such characters is fine. However, the “other” characters are delivered by emulating HEX input. Conclusion: unless your keyboard layout supports input of A LOT of characters without prefix keys, some buggy applications may skip characters when you Paste via Console’s UI: Alt-Space E P. (This is why I recommend using my keyboard layouts!)

我们还应该记住，Windows上的“替代的、更强大的”主机根本不是主机。它们不支持Console-I/O api，因此依赖这些api工作的程序将无法正常工作。(不过，只使用“文件- i /O api到控制台文件句柄”的程序可以很好地工作。)

微软的Powershell就是一个非主机的例子。我不用它;要进行实验，按下并释放WinKey，然后输入powershell。

(另一方面，有一些程序，如ConEmu或ANSICON，试图做更多的事情:他们“试图”拦截控制台i /O api，以使“真正的控制台应用程序”也能工作。这绝对适用于玩具示例程序;在现实生活中，这可能解决不了您的特定问题。实验。)

总结

设置字体，键盘布局(并可选地，允许十六进制输入)。 只使用通过Console-I/O api的程序，并接受Unicode命令行参数。例如，任何由cygwin编译的程序都可以。正如我已经说过的，CMD也很好。

UPD:最初，对于cp65001中的一个错误，我混淆了内核层和CRTL层(UPD²:和Windows用户模式API!)另外:Win8修复了这个错误的一半;我澄清了关于“更好的控制台”应用程序的部分，并添加了Python如何做到这一点的参考。

这个问题很烦人。我通常在文件名和文件内容中使用中文字符。请注意，我使用的是Windows 10，下面是我的解决方案:

如果在Windows 10上安装了Ubuntu bash，则显示文件名为dir或ls

设置该区域支持非utf8字符。 在此之后，控制台的字体将被更改为该地区的字体，它还将更改控制台的编码。

在完成以上步骤后，为了使用命令行工具显示UTF-8文件的文件内容

通过chcp 65001将页面更改为utf-8 更改为支持utf-8的字体，例如Lucida Console 使用type命令查看文件内容，如果你在Windows 10上安装了Ubuntu bash，可以使用cat命令查看 请注意，在将控制台的编码设置为utf-8后，我无法在cmd中使用中文输入法输入汉字。

最懒的解决方案:只使用控制台模拟器，如http://cmder.net/

从2019年6月开始，使用Windows 10，你将不必更改代码页。

参见“介绍Windows终端”(来自Kayla Cinnamon)和Microsoft/Terminal。 通过使用Consolas字体，将提供部分Unicode支持。

如Microsoft/Terminal issue 387中所述:

There are 87,887 ideographs currently in Unicode. You need all of them too? We need a boundary, and characters beyond that boundary should be handled by font fallback / font linking / whatever. What Consolas should cover: Characters that used as symbols that used by modern OSS programs in CLI. These characters should follow Consolas' design and metrics, and properly aligned with existing Consolas characters. What Consolas should NOT cover: Characters and punctuation of scripts that beyond Latin, Greek and Cyrillic, especially characters need complex shaping (like Arabic). These characters should be handled with font fallback.

我发现这个方法在新版本的Windows 10中很有用:

打开此功能:"Beta版:使用Unicode UTF-8支持全球语言"

控制面板->区域设置->管理选项卡->更改 系统区域设置…