Opened 9 years ago
Closed 9 years ago
#25360 closed Bug (needsinfo)
Django1.8 install error when using setuptools setup
| Reported by: | hsiao | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | 1.8 |
| Severity: | Normal | Keywords: | install |
| Cc: | django@… | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I wrote this in setup.py:
from setuptools import setup
setup(
......
zip_safe=False,
install_requires=['django==1.8.4'],
)
When I ran command $ python setup.py install,
I got this error:
Searching for django
Reading https://pypi.python.org/simple/django/
Best match: Django 1.8.4
Downloading https://pypi.python.org/packages/source/D/Django/Django-1.8.4.tar.gz
#md5=8eb569a5b9d984d9f3366fda67fb0bb8
Processing Django-1.8.4.tar.gz
error: [Errno 22] invalid mode ('wb') or filename: 'c:\\users\\user\\appdata\\local\\temp\\easy_install-sqik__\\Django-1.8.4\\tests\\staticfiles_tests\\apps\\test\\static\\test\\\xe2\x8a\x97.txt'
Same error occurs when I use easy_install to install django 1.8.
( I ran the script on windows7 )
Change History (4)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
The principle problem appears similar to that in #24761 in that staticfiles_tests includes files which are not safe across varying file systems/file formats/locales.
Using setup.py as an entrypoint to bootstrap a project seems like an OK way of doing things to me, even if the convention for many is to have requirements.txt or whatever for pip to use. That said, many re-usable packages will have an install_requires which includes a Django line, and the ecosystem hasn't crumbled amid a myriad of errors, so I'm inclined to suggest that the environment details are pertinent to diagnose if anything could be done.
comment:3 by , 9 years ago
| Cc: | added |
|---|
comment:4 by , 9 years ago
| Resolution: | → needsinfo |
|---|---|
| Status: | new → closed |
Are you on Python 2 or 3? (If 2, could you try 3?) I guess this could be poor support for Unicode filenames on setuptools, but I'm not too sure. It's unclear to me that it's a bug in Django that we can do something about. I think the Django ecosystem mostly uses pip these days.