mod_python support

[Kamil Gałuszka]

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.

Cheers

Kamil Gałuszka

[Alex Gaynor]

I'm -1 on this. If it's, in fact, just a normal WSGI container, we should add docs for it if it has any uptake, as we would for any other WSGI container, and I don't believe it has any uptake.

Alex

--
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 django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
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/cea5e59a-42a7-4084-91ab-8759da7d2f1d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

"I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero

GPG Key fingerprint: 125F 5C67 DFE9 4084

[Kamil Gałuszka]

I understand that and I agree that it maybe doesn't have any uptake. But, my reason for sending that information was question from today on django-users about mod_python support on Django. 

https://groups.google.com/forum/#!topic/django-users/449r3gUsN54

Cheers,

Kamil Gałuszka

2013/11/25 Alex Gaynor <alex....@gmail.com>

--
You received this message because you are subscribed to a topic in the Google Groups "Django developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/TWEhJTRJ5OA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-develop...@googlegroups.com.

To post to this group, send email to django-d...@googlegroups.com.
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/CAFRnB2U_f_fqC_c84aPsgWe6PoGVQjKy15X4rLNvPx0VpWMCLw%40mail.gmail.com.

[Ramiro Morales]

If it implements WSGI then there is no need to add or modify anything from the Django side. Both should be able to talk to each other using that protocol.

Now that specs like WSGI exist there is no point in going back one decade implementing interfaces to cater for one particular web server integration implementation.

Ramiro Morales
@ramiromorales

[Tom Evans]

On Mon, Nov 25, 2013 at 5:09 PM, Ramiro Morales <cra...@gmail.com> wrote:
> Now that specs like WSGI exist there is no point in going back one decade
> implementing interfaces to cater for one particular web server integration
> implementation.

Is that any worse than where we are now, using an interface that only
allows integration with apps written in one language? I'd hoped that
integrating web apps in to web servers had been solved by FCGI, but
along came python...

Cheers

Tom

PS - Not criticising any decision here, we use wsgi/mod_wsgi for our
python apps. it's just a pain to have to use something else for the
wordpress sites, something else for the perl sites (only have one of
these left now, thank $DEITY!)

[Russell Keith-Magee]

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 %-)