-
-
Notifications
You must be signed in to change notification settings - Fork 619
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
python 2.7 TypeError: environment can only contain strings #209
Comments
👍 |
This is how I fixed this problem with jupyter kernel http://ihorbobak.com/index.php/2017/12/13/pyspark-kernel-for-jupyter-in-python-2-7-windows/ but I do believe yours can be fixed the same way |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I have this error on python 2.7 on Windows when at the resolve cycle.
The resolver.py module sets its unicode literals from the future import, and also wants to inject PIP_EXISTS_ACTION in the os.environ which does not accept unicode data as keys, nor values.
This makes subprocess calls issued in pip fail, because os.environ cannot contain unicode data.
Other projects have had this problem:
pallets/werkzeug#467
and
celery/django-celery#344
Other technique seen also on stackoverflow.
One suggestion is to remove the unicode_literals future import and this seems the easiest fix as it supports both python 2.7 and 3.
The text was updated successfully, but these errors were encountered: