Opened 18 years ago

Closed 18 years ago

#5303 closed (fixed)

PythonImport (for handling eggs) can't be placed inside VirtualHost or Location

Reported by: anonymous Owned by: Jacob
Component: Documentation Version: dev
Severity: Keywords: mod_python, PythonImport, egg
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Placing PythonImport inside of <Location> (as it is recommended in the Install mod_python documentation of Django) leads to an error when apache loads it's conf-file. Placing it inside <VirtualHost> doesn't work either.

Reason:
PythonImport is a server config directive (compare ​http://www.modpython.org/pipermail/mod_python/2005-October/019272.html)

Quote from ​http://httpd.apache.org/docs/2.0/mod/directive-dict.html#Context

server config
This means that the directive may be used in the server configuration files (e.g., httpd.conf), but not within any <VirtualHost> or <Directory> containers. It is not allowed in .htaccess files at all.
<<<

All the best for now - and thanks for developing Django!

Wolfram

Change History (3)

by Simon G. <dev@…>, 18 years ago

Attachment: modpython.diff​ added

comment:1 by Simon G. <dev@…>, 18 years ago

Has patch: set
Keywords: mod_python added; miod_python Installation removed
Triage Stage: Unreviewed → Ready for checkin

Well spotted, thank you.

comment:2 by Adrian Holovaty, 18 years ago

Resolution: → fixed
Status: new → closed

(In [6034]) Fixed #5303 -- Fixed incorrect statement about PythonPath directive in docs/modpython.txt

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