Re: [Python-Dev] [Web-SIG] WSGI is now Python 3-friendly
At 01:44 PM 9/26/2010 -0700, Guido van Rossum wrote:
On Sun, Sep 26, 2010 at 12:47 PM, Barry Warsaw <barry@python.org> wrote:
On Sep 26, 2010, at 1:33 PM, P.J. Eby wrote:
At 08:20 AM 9/26/2010 -0700, Guido van Rossum wrote:
I'm happy approving Final status for the *original* PEP 333 and I'm happy to approve a new PEP which includes PJE's corrections.
Can we make it PEP 3333, then? ;-)
That works for me.
Go for it.
Shall I just "svn cp" it, then (to preserve edit history), or wait for the PEP editor do it?
Since you have commit privileges, just do it. The PEP editor position mostly exists to assure non-committers are not prevented from authoring PEPs. Please do add a prominent note at the top of PEP 333 pointing to PEP 3333 for further information on Python 3 compliance or some such words. Add a similar note at the top of PEP 3333 -- maybe mark up the differences in PEP 3333 so people can easily tell what was added. And move PEP 333 to Final status. --Guido On Sun, Sep 26, 2010 at 1:50 PM, P.J. Eby <pje@telecommunity.com> wrote:
At 01:44 PM 9/26/2010 -0700, Guido van Rossum wrote:
On Sun, Sep 26, 2010 at 12:47 PM, Barry Warsaw <barry@python.org> wrote:
On Sep 26, 2010, at 1:33 PM, P.J. Eby wrote:
At 08:20 AM 9/26/2010 -0700, Guido van Rossum wrote:
I'm happy approving Final status for the *original* PEP 333 and I'm happy to approve a new PEP which includes PJE's corrections.
Can we make it PEP 3333, then? ;-)
That works for me.
Go for it.
Shall I just "svn cp" it, then (to preserve edit history), or wait for the PEP editor do it?
-- --Guido van Rossum (python.org/~guido)
On Mon, Sep 27, 2010 at 6:56 AM, Guido van Rossum <guido@python.org> wrote:
Since you have commit privileges, just do it. The PEP editor position mostly exists to assure non-committers are not prevented from authoring PEPs.
Please do add a prominent note at the top of PEP 333 pointing to PEP 3333 for further information on Python 3 compliance or some such words. Add a similar note at the top of PEP 3333 -- maybe mark up the differences in PEP 3333 so people can easily tell what was added. And move PEP 333 to Final status.
Since PEP 333 is referred to as both by both its PEP number and as WSGI 1.0, should the new PEP explicitly state that PEP 3333 is WSGI 1.0.1? (i.e. not a full update, even to 1.1 status, just some small tweaks to make it usable in the Python 3 world along with some generally applicable clarifications). Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
participants (3)
-
Guido van Rossum -
Nick Coghlan -
P.J. Eby