setup.py encoding

[ghost]

Originally reported by: philip_thiem (Bitbucket: philip_thiem, GitHub: Unknown)

---

In compat.py:55 may choke if the setup.py is not compatible with the expected console (filesystem?) encoding when compile tries to read from the file object with unspecified encoding.

For example: wincertstore appears to have a BOM at the beginning of its setup.py
but on windows something is defaulting to cp932. Yielding:

UnicodeDecodeError: 'cp932' codec can't decode byte 0xef in position 0: illegal multibyte sequence

exec(compile(source, fn, 'exec'), globs, locs)

Produced doing: setup.py test

---

• Bitbucket: https://bitbucket.org/pypa/setuptools/issue/191

[ghost]

Original comment by philip_thiem (Bitbucket: philip_thiem, GitHub: Unknown):

---

Actually this might be failing in in the package scripts... will take a closer look.

[ghost]

Original comment by philip_thiem (Bitbucket: philip_thiem, GitHub: Unknown):

---

It fails during the setup.py loading (executing)... Specifically when setup.py is trying to read CHANGES.txt. upstream bug? The CHANGES.txt has the 0xfe at position zero which is being misread because the encoding isn't specified. m-time is 2-26-2014

[ghost]

Original comment by philip_thiem (Bitbucket: philip_thiem, GitHub: Unknown):

---

https://bitbucket.org/tiran/wincertstore/pull-request/3/read-readmetxt-and-changestxt-as-utf-8/diff

Sent a pull request to upstream, they don't have an issue tracker, if it doesn't get noticed, I can email.

[ghost]

Original comment by philip_thiem (Bitbucket: philip_thiem, GitHub: Unknown):

---

This got resolved it, would appear.