Unfriendly error message when unicode is passed to package_dir or packages #190
Labels
Comments
benjaoming
added a commit
to benjaoming/setuptools
that referenced
this issue
May 27, 2016
Problem encountered on Ubuntu 14.04 Fixes pypa#190 If people need to fix this without this patch, they have to wrap their package names in `str()` like so: ```python #!/usr/bin/env python # -*- coding: utf-8 -*- from __future__ import absolute_import, print_function, unicode_literals setup( # .... package_dir=[ str('package_name'), ] ) ```
benjaoming
added a commit
to benjaoming/setuptools
that referenced
this issue
Jun 2, 2016
benjaoming
added a commit
to benjaoming/setuptools
that referenced
this issue
Jun 2, 2016
millerdev
added a commit
to dimagi/commcare-cloud
that referenced
this issue
Sep 21, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally reported by: jaraco (Bitbucket: jaraco, GitHub: jaraco)
Adding
__future__.unicode_literals
causes setup.py scripts to fail. In the mailman project, here is an example error when running python2 setup.py build:A different error occurs when using 'develop':
Setuptools could make this error message nicer.
The text was updated successfully, but these errors were encountered: