This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: UnicodeDecodeError: 'cp949'
Type: Stage: resolved
Components: Windows Versions: Python 3.6
process
Status: closed Resolution: third party
Dependencies: Superseder:
Assigned To: Nosy List: Hojung An, paul.moore, steve.dower, tim.golden, zach.ware
Priority: normal Keywords:

Created on 2016-11-08 16:42 by Hojung An, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
unicode_error.jpg Hojung An, 2016-11-08 16:42
Messages (2)
msg280317 - (view) Author: Hojung An (Hojung An) Date: 2016-11-08 16:42
I have Python3.6 and when I try to install pyinstaller using (pip install pyinstaller) I receive error messages for:
1) UnicodeDecodeError: 'cp949'
2) Command 'python setup.py egg_info' failed with error code 1

When I inquired about this to webmaster@python.org they asked me to post it here as it seemed like a bug.
msg280322 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2016-11-08 17:16
Firstly, welcome to the tracker, and thanks for helping test the early releases of Python 3.6.

For future reference, it's much preferred if you can copy-paste error messages into the text of the message. Attaching large log files is okay, but screenshots should only really be used for things that are not text.

In this case, it would seem to be an issue with the pefile package. It is reading a file with a default encoding as part of its setup.py, but since the file appears to be part of its own package it really should specify the encoding of the file. It's likely that the file "works" under US English encoding, but obviously not for other encodings such as CP949. If the authors of pefile specify the encoding when they open the file, then this problem will go away.

(As it happens, I investigated the possibility of changing Python to handle this situation better, and unfortunately it is not feasible. We've provided the tools for authors to avoid these issues on their own, but we can't reasonably change how they work without breaking a lot of existing code. So it really needs to be fixed by the pefile authors here.)
History
Date User Action Args
2022-04-11 14:58:39adminsetgithub: 72826
2016-11-08 17:16:57steve.dowersetstatus: open -> closed
resolution: third party
stage: resolved
2016-11-08 17:16:29steve.dowersetmessages: + msg280322
2016-11-08 16:42:48Hojung Ancreate