Django

Code

Ticket #3842 (closed: fixed)

Opened 1 year ago

Last modified 1 year ago

Unclear wording in mod_python docs

Reported by: jon.i.austin@gmail.com Assigned to: jacob
Milestone: Component: Documentation
Version: SVN Keywords: mod_python
Cc: Triage Stage: Accepted
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

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"

Attachments

Change History

04/10/07 23:02:42 changed by SmileyChris

  • needs_better_patch changed.
  • stage changed from Unreviewed to Design decision needed.
  • summary changed from incorrect wording in "How to use Django with mod_python" ? to Unclear wording in mod_python docs.
  • needs_tests changed.
  • needs_docs changed.

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

04/24/07 02:49:27 changed by mtredinnick

  • stage changed from Design decision needed to Accepted.

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

04/25/07 06:16:36 changed by Simon G. <dev@simon.net.nz>

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

06/07/07 13:03:21 changed by jacob

  • status changed from new to closed.
  • resolution set to fixed.

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

Add/Change #3842 (Unclear wording in mod_python docs)




Change Properties
Action