Ian Bicking wrote:
> Phillip J. Eby wrote:
>
>>At 02:32 PM 4/28/2006 -0500, Ian Bicking wrote:
>>
>>>I'd like to include paste.lint with that as well (as wsgiref.lint or
>>>whatever). Since the last discussion I enumerated in the docstring all
>>>the checks it does. There's still some outstandin
It's not clear to me whether this means that Ian can just relicense his
code for me to slap into wsgiref and thence into Python by virtue of my own
PSF contribution form and the compatible license, or whether it means Ian
has to sign a form too.
At 09:25 PM 5/22/2006 -0700, Guido van Rossum wro
This explains what to do, and which license to use:
http://www.python.org/psf/contrib/
--Guido
On 5/22/06, Ian Bicking <[EMAIL PROTECTED]> wrote:
> Phillip J. Eby wrote:
> > At 02:32 PM 4/28/2006 -0500, Ian Bicking wrote:
> >> I'd like to include paste.lint with that as well (as wsgiref.lint or
Phillip J. Eby wrote:
> At 02:32 PM 4/28/2006 -0500, Ian Bicking wrote:
>> I'd like to include paste.lint with that as well (as wsgiref.lint or
>> whatever). Since the last discussion I enumerated in the docstring all
>> the checks it does. There's still some outstanding issues, mostly where
>> I
At 02:32 PM 4/28/2006 -0500, Ian Bicking wrote:
>I'd like to include paste.lint with that as well (as wsgiref.lint or
>whatever). Since the last discussion I enumerated in the docstring all
>the checks it does. There's still some outstanding issues, mostly where
>I'm not sure if it is too restric
On 5/2/06, Ian Bicking <[EMAIL PROTECTED]> wrote:
> 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
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 techniq
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: htt
> 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 mod_p
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 re
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:
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 th
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 should be applied, is situatio
On 30/04/2006, at 10:50 AM, Ian Bicking wrote:
> Phillip J. Eby wrote:
>> At 07:48 PM 4/28/2006 -0500, Ian Bicking wrote:
>>> One is not more complex than the other.
>>
>> The implementation has more moving parts, but I was talking about
>> conceptual complexity.
>>
>> The most common web servers
Phillip J. Eby wrote:
> At 07:48 PM 4/28/2006 -0500, Ian Bicking wrote:
>> One is not more complex than the other.
>
> The implementation has more moving parts, but I was talking about
> conceptual complexity.
>
> The most common web servers do not match path prefixes, they have
> directories a
> Perhaps this could go in Demo/wsgiref/?
Perhaps both Ian's and Phillip's examples could go into Demo/wsgiref/?
Bill
___
Web-SIG mailing list
Web-SIG@python.org
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe:
http://mail.python.org/mailman/op
At 07:48 PM 4/28/2006 -0500, Ian Bicking wrote:
>One is not more complex than the other.
The implementation has more moving parts, but I was talking about
conceptual complexity.
The most common web servers do not match path prefixes, they have
directories and files. You can't have /foo/bar wit
Phillip J. Eby wrote:
> At 05:47 PM 4/28/2006 -0500, Ian Bicking wrote:
>> It will still be only a couple lines less than prefix matching.
>
> That's beside the point. Prefix matching is inherently a more complex
> concept, and more likely to be confusing, without introducing much in
> the way
At 04:34 PM 4/28/2006 -0700, Titus Brown wrote:
>Hi, Phillip,
>
>I'm getting this error when I run the tests, with both Python 2.3 and
>2.4:
>
>==
>FAIL: testHeaderFormats (wsgiref.tests.test_handlers.HandlerTests)
>---
At 05:47 PM 4/28/2006 -0500, Ian Bicking wrote:
>It will still be only a couple lines less than prefix matching.
That's beside the point. Prefix matching is inherently a more complex
concept, and more likely to be confusing, without introducing much in the
way of new features. If I want to dis
On Fri, Apr 28, 2006 at 02:36:11PM -0400, Phillip J. Eby 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/
->
Phillip J. Eby wrote:
> At 04:04 PM 4/28/2006 -0500, Ian Bicking wrote:
>
>> I don't see why not to use prefix matching. It is more consistent with
>> the handling of the default application ('', instead of a method that
>> needs to be overridden), and more general, and the algorithm is only
>> b
At 04:04 PM 4/28/2006 -0500, Ian Bicking wrote:
>I don't see why not to use prefix matching. It is more consistent with
>the handling of the default application ('', instead of a method that
>needs to be overridden), and more general, and the algorithm is only
>barely more complex and not what I'd
Phillip J. Eby wrote:
>> I'd like to include paste.lint with that as well (as wsgiref.lint or
>> whatever). Since the last discussion I enumerated in the docstring all
>> the checks it does. There's still some outstanding issues, mostly where
>> I'm not sure if it is too restrictive (marked with
At 02:32 PM 4/28/2006 -0500, Ian Bicking wrote:
>Guido van Rossum wrote:
> > 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
> > receiv
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
27 matches
Mail list logo
