Re: [Web-SIG] PEP 444

t >> tests for the compression egress filter.) > > Georg Brandl has thus far been updating the canonical PEP on python.org. I > don't know how you get access to that. Basically, you don't -- you send updates to p...@python.org and we'll h

Re: [Web-SIG] Is PEP 3333 the final solution for WSGI on Python 3?

Am 24.10.2010 19:25, schrieb Guido van Rossum: > On Sun, Oct 24, 2010 at 10:17 AM, Georg Brandl wrote: >> Am 24.10.2010 17:58, schrieb Chris McDonough: >>> On Sun, 2010-10-24 at 17:16 +0200, Georg Brandl wrote: >>>> Am 24.10.2010 16:40, schrieb Chris McDonough: >

Re: [Web-SIG] Is PEP 3333 the final solution for WSGI on Python 3?

Am 24.10.2010 17:58, schrieb Chris McDonough: > On Sun, 2010-10-24 at 17:16 +0200, Georg Brandl wrote: >> Am 24.10.2010 16:40, schrieb Chris McDonough: >> > On Sun, 2010-10-24 at 10:17 +0300, Armin Ronacher wrote: >> > >> >> I have to admit that my interes

Re: [Web-SIG] Is PEP 3333 the final solution for WSGI on Python 3?

Am 24.10.2010 16:40, schrieb Chris McDonough: > On Sun, 2010-10-24 at 10:17 +0300, Armin Ronacher wrote: > >> I have to admit that my interest in Python 3 is not very high and I am >> most likely not the most reliable person when it comes to driving PEP 444 :) > > We should probably withdraw the

Re: [Web-SIG] PEP 444 (aka Web3)

Am 16.09.2010 23:07, schrieb James Mills: >> - the web3 name >> >> If there is any value in this PEP and we find something to decide on, >> there is no reason this couldn't be WSGI 2. But until it's just >> something a small part of the web-sig community worked on directly >> a separate name i

Re: [Web-SIG] PEP 444 (aka Web3)

Am 16.09.2010 20:00, schrieb Ian Bicking: > On Thu, Sep 16, 2010 at 12:35 PM, Guido van Rossum > > wrote: > > On Thu, Sep 16, 2010 at 10:01 AM, Ian Bicking > > wrote: > > Well, reiterating some things I've said before: > >

Re: [Web-SIG] WSGI for Python 3

Am 28.08.2010 13:13, schrieb Armin Ronacher: > Hi, > > On 2010-08-28 1:04 PM, Georg Brandl wrote: >> Let me just throw in here that it's *NOT* too late to do something about >> Python 3.2. It is not even in beta state yet, and I am very willing to >> introduce the

Re: [Web-SIG] WSGI for Python 3

Am 27.08.2010 01:37, schrieb Armin Ronacher: > Hi, > > Is there a status update on that now I missed? Did something decide on > bytes for the environment values or are we still unsure about that? > > From a discussion lately I had with Graham on #pocoo it seems like he > lost interest on supp

Re: [Web-SIG] Request for Comments on upcoming WSGI Changes

René Dudfield schrieb: > On Mon, Sep 21, 2009 at 4:27 PM, James Bennett > wrote: >> On Mon, Sep 21, 2009 at 10:19 AM, P.J. Eby >> wrote: >>> +1. I'd really rather not have the spec dictated by the need to work around >>> problems in the stdlib or language definition. Better to fix them ASAP.

Re: [Web-SIG] Request for Comments on upcoming WSGI Changes

René Dudfield schrieb: > On Mon, Sep 21, 2009 at 8:10 AM, Chris McDonough > wrote: >> >> OTOH, I suspect the Python 3 stdlib is still broken if it requires native >> strings in various places (and prohibits the use of bytes). > > yes, python3 stdlib should support 'str'(the old unicode), 'buffer

Re: [Web-SIG] Request for Comments on upcoming WSGI Changes

P.J. Eby schrieb: >>- Python 3 no longer implicitly converts between unicode and byte >>strings. This covers comparisons, the regular expression engine, >>all string functions and many modules in the stdlib. >>- The Python 3 stdlib radically moved to unicode for non unicode things >>

Re: [Web-SIG] Unicode in Python 3

René Dudfield schrieb: > On Sat, Sep 19, 2009 at 2:26 PM, Georg Brandl > wrote: >> René Dudfield schrieb: >> >>>>> Here is a snippet from the compat.py we used to port pygame to support >>>>> python2.3 through 3.1 >>>> How is that rela

Re: [Web-SIG] Unicode in Python 3

René Dudfield schrieb: >>> Here is a snippet from the compat.py we used to port pygame to support >>> python2.3 through 3.1 >> How is that related? >> > > Rather than using a 2to3 tool - which then makes you have two versions > of your code, making the code work in python 2.x and 3.x. 2to3 > out