Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Possible hint for developer setup of virtualenv #242

Open
trawick opened this issue Feb 10, 2016 · 1 comment
Open

Possible hint for developer setup of virtualenv #242

trawick opened this issue Feb 10, 2016 · 1 comment

Comments

@trawick
Copy link

trawick commented Feb 10, 2016

An idiom seen in some setup.py files in the wild is to set the long description to open('README.something').read() or something equivalent. Once README gets Unicode characters the installation of the package can fail in deployment because the default encoding for open is wrong. (I think this is a Python 3 default encoding difference when LANG is unset.)

Unsetting LANG around pip install can find this problem earlier. This could/should be in Makefile's setup and update targets.
@dpoirier
Copy link
Contributor

I know I've seen this failure at times too, but I'm wondering under what circumstances LANG wouldn't be set. Maybe on a minimal server-type Ubuntu installation vs. our usual full desktop installation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@trawick @dpoirier