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
[Phillip J. Eby]
> 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.
It's clearly best if Ian si
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
> Perhaps this could go in Demo/wsgiref/?
Perhaps both Ian's and Phillip's examples could go into Demo/wsgiref/?
Bill
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.o
> It still looks like an application of WSGI, not part of a reference
> implementation.
It seems to me that canonical exemplars are part of what a "reference"
implementation should include. Otherwise it would be a "standard"
implementation, which is considerably different.
Bill
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
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:
> At 01:19 PM 4/28/2006 -0700, Guido van Rossum wrote:
>
>> It still looks like an application of WSGI, not part of a reference
>> implementation. Multiple apps looks like an advanced topic to me; more
>> something that the infrastructure (Apache server or whatever) ought to
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
On 4/28/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 01:19 PM 4/28/2006 -0700, Guido van Rossum wrote:
> >It still looks like an application of WSGI, not part of a reference
> >implementation. Multiple apps looks like an advanced topic to me; more
> >something that the infrastructure (Apache
On 4/28/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> If it's small enough, I'd say to add this mapper to wsgiref.util, or if
> Guido is strongly set against it being in the code, we should at least put
> it in the documentation as an example of how to use 'shift_path_info()' in
> wsgiref.util.
At 01:19 PM 4/28/2006 -0700, Guido van Rossum wrote:
>It still looks like an application of WSGI, not part of a reference
>implementation. Multiple apps looks like an advanced topic to me; more
>something that the infrastructure (Apache server or whatever) ought to
>take care of.
I'm fine with a s
Guido van Rossum wrote:
> It still looks like an application of WSGI, not part of a reference
> implementation. Multiple apps looks like an advanced topic to me; more
> something that the infrastructure (Apache server or whatever) ought to
> take care of.
I don't understand the distinction between
It still looks like an application of WSGI, not part of a reference
implementation. Multiple apps looks like an advanced topic to me; more
something that the infrastructure (Apache server or whatever) ought to
take care of.
I don't expect you to agree with me. But I don't expect you to be able
to
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
Guido van Rossum wrote:
>> I think another useful addition would be some prefix-based dispatcher,
>> similar to paste.urlmap (but probably a bit simpler):
>> http://svn.pythonpaste.org/Paste/trunk/paste/urlmap.py
>
>
> IMO this is getting into framework design. Perhaps something like this
> could
On 4/28/06, Ian Bicking <[EMAIL PROTECTED]> 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
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
> received by web framework makers and users.
>
> As a supplemen
24 matches
Mail list logo