New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
package cannot be built in non utf-8 environments #55
Comments
Let's try that as an attachment to avoid bitbucket wrapping the console output. Original comment by: Barry Warsaw |
To some extent, this has been fixed in the latest tip. I'm able to run setup.py --help without an error, but if I try to build the distribution or otherwise generate egg_info, it fails with an encode error in distutils. {{{ Apparently, [[https://github.com/pypa/virtualenv/issues/201|it's not possible to include international characters in a long description]]. Original comment by: Jason R. Coombs |
Removed non-ascii characters from CHANGES.txt. Fixes #55. → <> Original comment by: Jason R. Coombs |
This patch adds a job that is able to accurately signal whether all the expectations of the required jobs to succeed are met. This job can then be used as a source of truth for judging whether "CI passes" and can be used in the branch protection. It also plays a role of a convenient "gate" — this is the only job that would have to be listed in the branch protection as opposed to listing every single job name generated by the test matrix (and they all have different names — it's not possible to just select one `test` job name). Ref: https://github.com/re-actors/alls-green#why
On the Ubuntu build daemons, $LC_ALL is C which causes Python 3's sys.getfilesystemencoding() to return 'ascii' instead of 'utf-8'. This breaks setup.py because of the non-ascii characters in CHANGES.txt, so you get a dreaded UnicodeDecodeError:
The text was updated successfully, but these errors were encountered: