On Tue, Sep 21, 2010 at 11:09 AM, P.J. Eby <pje at telecommunity.com> wrote: > After all, even if PEP 333 is ultimately replaced by PEP 444, it's probably > a good idea to have *some* sort of WSGI 1-ish thing available on Python 3, > with bytes/unicode and other matters settled. Indeed. Though I generally like the direction that PEP 444 is going in, I know that writing specs is *HARD*. I think having something that works on Python 3 in time for the 3.2 release is a much bigger deal than having an WSGI2 (or whatever) done. This is classic "the perfect is the enemy of the good" territory. Let's get "the good" done and *then* spend time working on "the perfect". Jacob
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4