Opened 14 years ago

Closed 13 years ago

Last modified 12 years ago

#165 closed defect (wontfix)

Should mod_python config use PythonOption instead of SetEnv for settings?

Reported by: Manuzhai Owned by: Adrian Holovaty
Component: Core (Other) Version:
Severity: normal Keywords:
Cc: django@… Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


I'm not sure what does this for performance (probably not bad, though), but it surely ameliorates compatibility with mod_python-2 (and therefore apache-1, a whole suite of webhosts). Why was SetEnv chosen in the first place?

Change History (2)

comment:1 Changed 13 years ago by Steadicat

Cc: django@… added

comment:2 Changed 13 years ago by Jacob

Resolution: wontfix
Status: newclosed

We chose SetEnv to limit the dependance on mod_python as much as possible; this isn't going to change unless there's a compelling reason to use PythonOption instead.

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