Opened 16 years ago
Closed 16 years ago
#8717 closed (wontfix)
Slight change to installation guide
| Reported by: | blackhatrob | Owned by: | |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
In the installation guide for the SVN piece, you mention the use of PYTHONPATH. Why not go ahead and mention that instead of creating symlinks to the svn django bin location, just add the path to the user's PATH variable in their .bashrc:
i.e.
PYTHONPATH=/home/blackhatrob/source/svn/django_trunk:$PYTHONPATH
PATH=/home/blackhatrob/source/svn/django_trunk/django/bin:$PATH
export PYTHONPATH PATH
This way, you do not need any elevated privileges to download and develop django projects.
Change History (3)
comment:1 by , 16 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 16 years ago
| Owner: | removed |
|---|---|
| Status: | assigned → new |
comment:3 by , 16 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
We mention PYTHONPATH already. If people are comfortable working with environment variables, they know they can put them into
.bashrcor.bash_profile(the latter is preferable if you're appending to an environment variable so that subshells don't end up with one copy of the addition for each level of subshell, by the way).We can't cover every possible install option. We add this and somebody will ask what about tcsh? Or what about explicit windows instructions and so on. At some point, we have to assume some base level of knowledge and if you don't have that knowledge we provide one way to do the installation and Google and comp.lang.python and django-users will help with the rest.