#13820: Deprecate mod_python support ------------------------------------------------+--------------------------- Reporter: rcoup | Owner: nobody Status: new | Milestone: 1.3 Component: HTTP handling | Version: SVN Keywords: mod_python, mod_wsgi, wsgi, apache | Stage: Unreviewed Has_patch: 0 | ------------------------------------------------+--------------------------- As proposed & discussed in the [http://groups.google.co.nz/group/django- developers/browse_thread/thread/5e39c24fc5f0d98a/5d5ca7f91ebe49f5 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 -- Ticket URL: <http://code.djangoproject.com/ticket/13820> Django <http://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.
