Opened 13 years ago
Closed 13 years ago
#17578 closed Bug (fixed)
Explicitly invoke python for setup.py for Windows users
| Reported by: | Owned by: | Zbigniew Siciarz | |
|---|---|---|---|
| Component: | Documentation | Version: | 1.4-alpha-1 |
| Severity: | Normal | Keywords: | |
| Cc: | Gandi | Triage Stage: | Ready for checkin |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
Details of fault seen:
http://forums.degreez.net/viewtopic.php?f=3&t=7084
Suggested fix:
The last words of step 4 should be "python setup.py install" instead of just "setup.py install" in this page
https://docs.djangoproject.com/en/dev/topics/install/#installing-an-official-release
Attachments (1)
Change History (10)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
| Summary: | Explicitly involke python for setup.py for Windows users → Explicitly invoke python for setup.py for Windows users |
|---|
comment:3 by , 13 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|---|
| Type: | Uncategorized → Bug |
comment:4 by , 13 years ago
The "python" prefix is neccessary if you install Django in virtualenv (after executing activate.bat). Otherwise it installs Django to systemwide site-packages.
(django_install) C:\Users\USER\v\django_install\dist\Django-1.3.1>setup.py install ... loads of stuff printed ... Writing D:\Python27\Lib\site-packages\Django-1.3.1-py2.7.egg-info (django_install) C:\Users\USER\v\django_install\dist\Django-1.3.1>python setup.py install ... loads of stuff printed again... Writing C:\Users\USER\v\django_install\Lib\site-packages\Django-1.3.1-py2.7.egg-info
So it would make sense to mention "python setup.py install" explicitely.
comment:5 by , 13 years ago
As jezdez pointed out at the Django sprint, there is an issue when the path to Python executable is not on PATH. An old ticket #4878 mentioned this issue, but it was discarded in favor of a new ticket. The patch adds a note about neccessary modifications to the PATH.
comment:6 by , 13 years ago
| Owner: | changed from to |
|---|
comment:7 by , 13 years ago
| Has patch: | set |
|---|
comment:8 by , 13 years ago
| Cc: | added |
|---|---|
| Triage Stage: | Accepted → Ready for checkin |
| Version: | 1.3 → 1.4-alpha-1 |
Well, the forum post you are linking to is not supporting your request. The user did type "python setup.py" instead of "python setup.py install". But I guess a "setup.py install" would have worked the same way. I'm not so much familiar with Windows to finally decide if explicitely calling python is recommended or not.