You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
running build
running build_py
Traceback (most recent call last):
File "setup.py", line 112, in <module>
test_suite = 'nose2.collector.collector',
File "C:\Program Files\Python27\lib\distutils\core.py", line 152, in setup
dist.run_commands()
File "C:\Program Files\Python27\lib\distutils\dist.py", line 953, in run_commands
self.run_command(cmd)
File "C:\Program Files\Python27\lib\distutils\dist.py", line 972, in run_command
cmd_obj.run()
File "C:\Program Files\Python27\lib\distutils\command\build.py", line 127, in run
self.run_command(cmd_name)
File "C:\Program Files\Python27\lib\distutils\cmd.py", line 326, in run_command
self.distribution.run_command(command)
File "C:\Program Files\Python27\lib\distutils\dist.py", line 972, in run_command
cmd_obj.run()
File "build\bdist.win-amd64\egg\setuptools\command\build_py.py", line 42, in run
File "C:\Program Files\Python27\lib\distutils\command\build_py.py", line 372, in build_packages
self.build_module(module, module_file, package)
File "build\bdist.win-amd64\egg\setuptools\command\build_py.py", line 60, in build_module
File "C:\Program Files\Python27\lib\distutils\command\build_py.py", line 333, in build_module
"'package' must be a string (dot-separated), list, or tuple")
TypeError: 'package' must be a string (dot-separated), list, or tuple
A different error occurs when using 'develop':
running develop
error: 'egg_base' must be a directory name (got `src`)
Problem encountered on Ubuntu 14.04
Fixespypa#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'),
]
)
```
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: