Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.albasani.net!weretis.net!feeder4.news.weretis.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed1a.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Date: Sun, 29 Mar 2015 21:50:59 -0600
From: Carl Meyer <carl@oddbird.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: python-list@python.org
Subject: Re: Python 3 lack of support for fcgi/wsgi.
References: <mf9hu0$jpu$1@dont-email.me> <mailman.313.1427656270.10327.python-list@python.org> <55185E5D.5080604@animats.com> <mf9uou$8k0$1@dont-email.me> <85pp7r4dj8.fsf@benfinney.id.au> <5518C342.9010504@gmail.com>
In-Reply-To: <5518C342.9010504@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sXxDIiOgTQbdmGhGKx74bvMnser3SDSft"
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.329.1427687476.10327.python-list@python.org>
Lines: 65
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:88312

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--sXxDIiOgTQbdmGhGKx74bvMnser3SDSft
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 03/29/2015 09:30 PM, Michael Torrie wrote:
> What does this have to do with Python itself?  I'm not completely sure,=

> but maybe it's about the Python community.  What's the way forward?  I
> have no idea.  At the very least John is frustrated by the community's
> lack of apparent interest in fixing problems in the greater python
> ecosystem when it comes to Python 3.

I think one could easily draw far too broad a conclusion from John's
report here. The title of the thread says "lack of support for
fcgi/wsgi", but AFAICT the content of the report, and the thread, is
entirely about FCGI. In my experience, WSGI under Python 3 works very
well these days, and all of the popular WSGI servers (gunicorn,
mod_wsgi, uwsgi, waitress, ...) run just fine under Python 3. I've
deployed several Django applications into production on Python 3 (using
WSGI) with no issues.

FastCGI is a different story. I do some Django support on #django and on
django-users, and I see very few people deploying with FastCGI anymore;
almost everyone uses WSGI (and when we see someone using FastCGI, we
encourage them to switch to WSGI). In fact, the FastCGI support in
Django itself is deprecated and will be removed in Django 1.9. So I am
not at all surprised to hear that the Python FastCGI libraries are
relatively poorly maintained.

And it is true and unsurprising that when a particular library is no
longer maintained, it will probably be in better shape on Python 2 than
on Python 3, because Python 2 is older.

So when it comes to "the community's interest in fixing problems" or
John's assertion that "nobody uses this stuff," in both cases I think
it's far more about FastCGI vs WSGI than it's about Python 2 vs 3.

Carl


--sXxDIiOgTQbdmGhGKx74bvMnser3SDSft
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVGMgjAAoJEC0ft5FqUuEhajgQAI3fO1tJ3C6fVCcXC+ka5M8o
DGsQ+sHpgaiAHNqBqJzA9luaxXlh6kTYeGp/opsM3isUGZ3xhK+bZXJXwwITQWJQ
kB/pym8hWAzt17lGAd46Rc7tOt32qLoUPjFLseLMPBWOYvgAE/ehrPHvXdtw/hYA
cLXs6UAHEXuQze7FpzfbE01ZRelMjoPSNNSViGNYxcrXwbRNWGgwJYeg18dmE2u4
Kskc+SwteUOIiN8LD608k3OGFNddFT4+pkdrN/Ss49/GGrZ/vbVYsc1t8zmNW+/a
cxSPER0/ZIbyxhnqt9n97qIC9opg3h8cW7HdgSwPXbcUMiQd4J5IfqjKdVTGsII7
QuVXgwMRFCTSXX3jP7WqJuEzCA80aYBPoON4lYYyyPWXy00ZFjvRrcEgg2WX+vQj
cLguhuDeaox68KXsIUCw3ErrJ0wQWvtWCMJ0+I6ZPvREOHjbCMK0+fFeOM6sTf+E
P8uu/C3pZNeXNcX8kgcbWCRSmxTRIav6p6KjKhIakyI9TMAonMDR7UAzJTZBQvsk
mv5MOcxxpFW0a2sO5SxV7bwChvBKRcExDa9ZawSNHsQpZGE6mcsY4Yf0rpEij0h5
a8ubMjO1zWU1QW3Tij1yRHaVSabCqG2ex667lhUTpTGFWOsjgSRfkgQ3sy6BTC1Z
8Fo9cQyr7BH3jGMWrV2B
=tN1X
-----END PGP SIGNATURE-----

--sXxDIiOgTQbdmGhGKx74bvMnser3SDSft--