[Python-Dev] [Web-SIG] WSGI is now Python 3-friendly (original) (raw)
Guido van Rossum guido at python.org
Sun Sep 26 22:56:54 CEST 2010
- Previous message: [Python-Dev] [Web-SIG] WSGI is now Python 3-friendly
- Next message: [Python-Dev] [Web-SIG] WSGI is now Python 3-friendly
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 at 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 at 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)
- Previous message: [Python-Dev] [Web-SIG] WSGI is now Python 3-friendly
- Next message: [Python-Dev] [Web-SIG] WSGI is now Python 3-friendly
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]