On Tue, Jan 4, 2011 at 12:13 AM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > On Sun, Jan 2, 2011 at 9:21 AM, Guido van Rossum <gu...@python.org> wrote: >> Although [PEP 3333] is still marked as draft, I personally think of it >> as accepted; [...] > > What does it take to get PEP 3333 formally marked as accepted? Is > there anything I can do to push that process forward? > > The lack of a WSGI answer on Py3 is the main thing that's keeping me, > personally, from feeling excited about the platform. Once that's done > I can feel comfortable coding to it -- and browbeating those who don't > support it. > > I understand that PEP 444/Web3/WSGI 2/whatever might be a better > answer, but it's clearly got some way to go. In the meantime, what's > next to get PEP 3333 officially endorsed and accepted? > > Jacob
I we pep3333 is considered accepted, I will start the port of gunicorn based on it too. It shouldn't be hard since we are using our own http parser. - benoit _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
