Opened 9 years ago

Closed 8 years ago

#3842 closed (fixed)

Unclear wording in mod_python docs

Reported by: jon.i.austin@… Owned by: jacob
Component: Documentation Version: master
Severity: Keywords: mod_python
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


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 Changed 9 years ago by SmileyChris

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Summary changed from incorrect wording in "How to use Django with mod_python" ? to Unclear wording in mod_python docs
  • Triage Stage changed from Unreviewed to Design decision needed

It would probably be more clear if that code example repeated the whole above <Location> code (would make for easier copy/pasting too ;))

comment:2 Changed 9 years ago by mtredinnick

  • Triage Stage changed from Design decision needed to Accepted

This is a reasonable change. I've wondered about making it in the past.

comment:3 Changed 9 years ago by Simon G. <dev@…>

#4110 is a duplicate. We should clarify the sys.path issue somehow

comment:4 Changed 8 years ago by jacob

  • Resolution set to fixed
  • Status changed from new to closed

(In [5434]) Fixed #3842 - clarified PythonPath directive in modpython.txt. Thanks, jon.i.austin@….

Note: See TracTickets for help on using tickets.
Back to Top