#13820 closed (fixed)
Deprecate mod_python support
Description ¶
As proposed & discussed in the 1.3 Start deprecating mod_python? thread on Django-Developers, here's the ticket.
For the rationale, see the mailing list thread.
Things to do:
- Make use of mod_python raise a
PendingDeprecationWarning - Add "don't use this" messages to the deployment docs, and remove altogether from the install/etc documentation
- Update wiki pages to steer people away from mod_python
- Add to the Deprecation timeline and release notes
Hotshot Profiler ¶
From Russell in the same mailing-list thread:
The only catch I can think of that hasn't been raised is the hotshot profiling handler; it's currently dependent on the modpython handler. I don't think there's a whole lot of extra work required to port it over, but it's worth putting on the todo list so it isn't forgotten.
Graham D also posted a wsgi equivalent piece of code.
Options:
- port to WSGIHandler
- move the wsgi-equivalent code to the docs, or the wiki, or django-snippets; and remove from the codebase altogether when removing mod_python
Change History (6)
comment:1 by , 15 years ago
| Needs documentation: | set |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
by , 15 years ago
| Attachment: | django-13820.diff added |
|---|
Patch to add warnings and update docs to piss on mod_python
comment:3 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:4 by , 15 years ago
GAH! My apologies - the patch credit goes to Joshua Gisberg, not Robert. Thanks to Robert for the report, and Joshua for the patch.
Moving to Accepted based on +1's from Jacob & Russell in the django-developers thread