Opened 18 years ago
Closed 17 years ago
#3842 closed (fixed)
Unclear wording in mod_python docs
Reported by: | Owned by: | Jacob | |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Keywords: | mod_python | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Seems like the below section should be removed and PythonPath "['/path/to/project'] + sys.path"
should simply be appended to the <Location... apache directive under Basic Configuration.
I assume by PYTHONPATH an environment variable is meant (which does not exist under my bash env
), but in order for apache/mod_python to see my project I did indeed have to add the below code directly within <Location...
Basic Configuration ... Also, if you’ve manually altered your PYTHONPATH to put your Django project on it, you’ll need to tell mod_python: PythonPath "['/path/to/project'] + sys.path"
Change History (4)
comment:1 by , 18 years ago
Summary: | incorrect wording in "How to use Django with mod_python" ? → Unclear wording in mod_python docs |
---|---|
Triage Stage: | Unreviewed → Design decision needed |
comment:2 by , 18 years ago
Triage Stage: | Design decision needed → Accepted |
---|
This is a reasonable change. I've wondered about making it in the past.
comment:4 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
(In [5434]) Fixed #3842 - clarified PythonPath directive in modpython.txt. Thanks, jon.i.austin@….
It would probably be more clear if that code example repeated the whole above
<Location>
code (would make for easier copy/pasting too ;))