[Web-SIG] Declaring PEP 3333 accepted (was: PEP 444 != WSGI 2.0)

P.J. Eby pje at telecommunity.com
Tue Jan 4 02:27:09 CET 2011


At 04:43 PM 1/3/2011 -0800, Guido van Rossum wrote:
>On Mon, Jan 3, 2011 at 3:13 PM, Jacob Kaplan-Moss <jacob at jacobian.org> wrote:
> > On Sun, Jan 2, 2011 at 9:21 AM, Guido van Rossum <guido at 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?
>
>I haven't heard anyone speak up against it, ever, since it was
>submitted. If no-one speaks up in the next 24 hours consider it
>accepted (and after that delay, anyone with SVN privileges can mark it
>thus).

There are a few minor changes to the code samples needed to make them 
proper Python 3; I just checked in the hairiest of them, though.



More information about the Web-SIG mailing list