#22235 closed Cleanup/optimization (fixed)
pip can install from tarballs as well
| Reported by: | Owned by: | gregloy | |
|---|---|---|---|
| Component: | *.djangoproject.com | Version: | |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | yes | UI/UX: | no |
Description
The download page recommends downloading the tarball and unpacking it and running setup.py.
There's no reason to do so anymore since pip can install python packages from tarballs.
The documentation should be changed in my opinion.
Change History (6)
comment:1 by , 11 years ago
| Component: | Documentation → *.djangoproject.com |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:3 by , 11 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:4 by , 11 years ago
| Patch needs improvement: | set |
|---|
As noted in the pull request, you also need to modify the settings to activate the request context processor so that the request object is available in the context.
I would also suggest that we only keep install instructions with pip and get rid of the tar xvzf ... ones (both for stable and preview versions).
comment:5 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Assuming there are no reasons why this might be more insecure (which I personally don't see) I agree that for alphas/betas using pip to install them is much easier.
The relevant source code is actually in the djangoproject.com repository - https://github.com/django/djangoproject.com/blob/master/templates/releases/download.html#L28-30