On Tue, Nov 26, 2013 at 12:36 AM, Kamil Gałuszka <[email protected]>wrote:
> Hi ! > > I wanted to post this in old topic from 2010 but Google always gives me an > error on posting so I can't do that there. (soory for that!) > > I know that mod_python support was dropped long time ago but I think this > information should be noted to core developers. There is new release of > mod_python that support WSGI and is adding Python 3. Maybe we should > reconsider adding it to django (only documentation I think since if it has > WSGI support we maybe don't need do anything more. But I'm not sure so I > could be wrong.)? > > Here is WSGI handler to mod_python: > http://modpython.org/live/current/doc-html/handlers.html#wsgi-handler > > New version was released 13 November http://modpython.org/. I think > someone started refactoring old mod_python and moved project to github. > > Echoing the sentiment of Alex and Ramiro -- I'm -1 on this too, at least at the moment. Once upon a time, mod_python was "the way"; despite that history, it's now in the category of "experimental edge case". mod_python's past history doesn't automatically grant it re-entry into Django's core. Based on Grisha's comments about his intended direction with the project, I *can* see a set of circumstances where we *might* re-add a mod_python backend. He's talking about mod_python being more about a "Python interface to Apache" rather than a traditional website container. To that end, I can imagine that at some point, it might be possible to expose HTTP connection features that don't fit into the WSGI model. *If* that happens, *and* those features are compelling, *and* mod_python has a stable implementation of those features, then adding a formal mod_python interface back to Django's core *might* be called for. In the meantime -- if someone wants to experiment with a new mod_python backend with the aim of playing with these nifty new features, I'd encourage you to do so. This sort of experimentation *should* be able to live external to Django's core. If it can't, then propose the changes you need to make external experimentation possible. If, in the fullness of time, it turns out that merging is called for, that external project would become the obvious candidate for a merge into trunk. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq848TyQ_d%2BRxrdMGThtTVkO%2Bg%3D%3DO5gc04NJp7vhK4LtOgeg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
