#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 |
Description
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 by , 19 years ago
| Cc: | added |
|---|
comment:2 by , 19 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
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.