Code

Opened 9 years ago

Closed 9 years ago

Last modified 8 years ago

#165 closed defect (wontfix)

Should mod_python config use PythonOption instead of SetEnv for settings?

Reported by: Manuzhai Owned by: adrian
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: UI/UX:

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?

Attachments (0)

Change History (2)

comment:1 Changed 9 years ago by Steadicat

  • Cc django@… added

comment:2 Changed 9 years ago by jacob

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

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.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.