At 11:03 AM 4/28/2006 -0700, Guido van Rossum wrote:
>(I'm asking Phillip to post the URL for the current
>source; searching for it produces multiple repositories.)
Source browsing: http://svn.eby-sarna.com/wsgiref/
Anonymous SVN: svn://svn.eby-sarna.com/svnroot/wsgiref
___
> I'm inviting people to discuss the addition of wsgiref to the standard
> library. I'd like the discussion to be finished before a3 goes out;
+1.
I think it's faily low-risk. WSGI has been discussed and implemented
for well over a year; there are many working implementations of the
spec. Addin
PEP 333 specifies WSGI, the Python Web Server Gateway Interface v1.0;
it's written by Phillip Eby who put a lot of effort in it to make it
acceptable to very diverse web frameworks. The PEP has been well
received by web framework makers and users.
As a supplement to the PEP, Phillip has written a
On 4/22/06, A.M. Kuchling <[EMAIL PROTECTED]> wrote:
> What with all the discussion that resulted from setuptools, we should
> probably also discuss the suggestion to add wsgiref to the standard
> library. PEP 356 doesn't have many details about what's under consideration.
>
> (wsgiref is an imple
What with all the discussion that resulted from setuptools, we should
probably also discuss the suggestion to add wsgiref to the standard
library. PEP 356 doesn't have many details about what's under consideration.
(wsgiref is an implementation of the WSGI interface defined in PEP 333.
I believe
