[Chicago] Status of wsgi

Nolan Brubaker nolan.brubaker at gmail.com
Tue Oct 9 19:57:18 CEST 2012

From what I understand, all the Python 3 WSGI work is happening based on PEP 3333, which makes some changes to account for the distinctions between byte arrays and strings for Python 3.

The Pyramid framework is already Python 3 compatible, and Django's working on it.

On Oct 9, 2012, at 1:09 PM, Garrett Smith <g at rre.tt> wrote:

> It's been a number of years now since I've built web stuff in Python
> (forgive me) but last I checked, wsgi was still the dominant force in
> Python land for anything web.
> With Python 3, web sockets, crazed fixation on async socket servers,
> etc. I'm wondering if that's still the case. Has wsgi been able to
> keep up with the latest trends, or is it falling over? Is there
> another standard in Python land that shows more promise or growth
> trajectory?
> I ask because I'm researching some options for a similar spec for the
> Erlang community -- and I'd like to catalog the good and bad of
> Python's (much more mature) web ecosystem.
> Garrett
> _______________________________________________
> Chicago mailing list
> Chicago at python.org
> http://mail.python.org/mailman/listinfo/chicago

More information about the Chicago mailing list