Hello all,
I've been following the discussion around adding wsgiref to the stdlib and
it sounds like a very good idea. However I'm a little concerned as it
seems only wsgiref has been suggested to be included. I wonder if you guys
intend to review other implementations before going ahead? I ask
On 4/28/06, Phillip J. Eby [EMAIL PROTECTED] wrote:
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:
On 5/2/06, Sylvain Hellegouarch [EMAIL PROTECTED] wrote:
I've been following the discussion around adding wsgiref to the stdlib and
it sounds like a very good idea. However I'm a little concerned as it
seems only wsgiref has been suggested to be included. I wonder if you guys
intend to review
Anything that could be considered of sufficiently industrial strength
to be secure and scalable in production would necessarily be such a
large project, such a complex code base, and have such different
release cycle that it would not make a good standard library
candidate. (Think
At 02:48 PM 5/2/2006 +0100, Paul Moore wrote:
On 4/28/06, Phillip J. Eby [EMAIL PROTECTED] wrote:
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:
Luke Arno wrote:
I don't pipe up much but dispatch has been on my
mind for a while as I have been working on this:
http://lukearno.com/projects/selector/
I think dispatching is best left as an (obvious) exercise
to the reader. What dispatching makes sense, what
metaphor or technique