python: unicode in Windows terminal, encoding used?
Solution 1
Unicode is not an encoding. You encode into byte strings and decode into Unicode:
>>> '\x89'.decode('cp437')
u'\xeb'
>>> u'\xeb'.encode('cp437')
'\x89'
>>> u'\xeb'.encode('utf8')
'\xc3\xab'
The windows terminal uses legacy code pages for DOS. For US Windows it is:
>>> import sys
>>> sys.stdout.encoding
'cp437'
Windows applications use windows code pages. Python's IDLE will show the windows encoding:
>>> import sys
>>> sys.stdout.encoding
'cp1252'
Your results may vary.
Solution 2
Avoid Windows Terminal
I'm not going out on a limb by saying the 'terminal' more appropriately the 'DOS prompt' that ships with Windows 7 is absolute junk. It was bad in Windows 95, NT, XP, Vista, and 7. Maybe they fixed it with Powershell, I don't know. However, it is indicative of the kind of problems that were plaguing OS development at Microsoft at the time.
Output to a file instead
Set the PYTHONIOENCODING
environment variable and then redirect the output to a file.
set PYTHONIOENCODING=utf-8
./myscript.py > output.txt
Then using Notepad++ you can then see the UTF-8 version of your output.
Install win-unicode-console
win-unicode-console can fix your problems. You should try it out
pip install win-unicode-console
If you are interested in a through discussion on the issue of python and command-line output check out Python issue 1602. Otherwise, just use the win-unicode-console package.
py -m run script.py
Runs it per script or you can follow their directions to add win_unicode_console.enable()
to every invocation by adding it to usercustomize
or sitecustomize
.
Solution 3
In case others get this page when searching Easiest way is to set the codepage in the terminal first
CHCP 65001
then run your program.
working well for me. For power shell start it with
powershell.exe -NoExit /c "chcp.com 65001"
Its from python: unicode in Windows terminal, encoding used?
Solution 4
Read through this python HOWTO about unicode after you read this section from the tutorial
Creating Unicode strings in Python is just as simple as creating normal strings:
>>> u'Hello World !'
u'Hello World !'
To answer your first question, they are different because only when using u''
are you creating a unicode string.
2nd question:
sys.getdefaultencoding()
returns the default encoding
But to quote from link:
Python users who are new to Unicode sometimes are attracted by default encoding returned by sys.getdefaultencoding(). The first thing you should know about default encoding is that you don't need to care about it. Its value should be 'ascii' and it is used when converting byte strings StrIsNotAString to unicode strings.
Solution 5
It appears you are using code page CP850, which makes sense as this is the historical code page for DOS which has been carried forward to the terminal window.
>>> s
'\x89'
>>> us=unicode(s,'CP850')
>>> us
u'\xeb'
Rabarberski
Updated on August 05, 2022Comments
-
Rabarberski almost 2 years
I am using the Python interpreter in Windows 7 terminal.
I am trying to wrap my head around unicode and encodings.I type:
>>> s='ë' >>> s '\x89' >>> u=u'ë' >>> u u'\xeb'
Question 1: Why is the encoding used in the string
s
different from the one used in the unicode stringu
?I continue, and type:
>>> us=unicode(s) Traceback (most recent call last): File "<stdin>", line 1, in <module> UnicodeDecodeError: 'ascii' codec can't decode byte 0x89 in position 0: ordinal not in range(128) >>> us=unicode(s, 'latin-1') >>> us u'\x89'
Question2: I tried using the
latin-1
encoding on good luck to turn the string into an unicode string (actually, I tried a bunch of other ones first, includingutf-8
). How can I find out which encoding the terminal has used to encode my string?Question 3: how can I make the terminal printHmm, stupid me.ë
asë
instead of'\x89'
oru'xeb'
?print(s)
does the job.I already looked at this related SO question, but no clues from there: Set Python terminal encoding on Windows
-
jfs almost 8 years
-
-
Rabarberski almost 13 yearsGood point about 'unicode object has no encoding'. I am not on a russian version of Windows, but an English one.
-
Rabarberski almost 13 yearsOK. But why then, when i turn the string
s
into a unicode string by doingus=unicode(s, 'latin-1')
is the resulting unicode stringus
not shown asu'\xeb'
-
Rabarberski almost 13 yearsThe linked presentation is indeed very good (at least for me)
-
Daniel Roseman almost 13 yearsAs Mark says, your encoding is probably CP850 rather than Latin-1.
-
Rabarberski almost 13 yearsThanks for the
sys.stdout.encoding
tip. Now it is clear to me how I can determine the encoding used in the terminal -
jfs about 9 years
print
already works for the OP. The issue is not the console encoding. -
Cameron Lowell Palmer about 8 yearsThat is a sad state of affairs and central to what plagues the OS
-
Mark Ransom almost 7 yearsStarting with Python 3.6 the Windows console is much more usable. Outputting to the console bypasses the code page nonsense entirely and works directly with Unicode.
-
Cameron Lowell Palmer almost 7 yearsThat's good to know. Next time I'm doing some python development for a Windows shop I'll try and push them forward