Re: [Web-SIG] Python 3 / PEP 3333 (was: PEP 444 / WSGI 2 Async)

2011-01-07 Thread Jacob Kaplan-Moss
On Fri, Jan 7, 2011 at 1:23 AM, Alice Bevan–McGregor wrote: > Other than mod_wsgi, are there any PEP -compliant (or near-compliant) > components in the wild?  Enough to bring a framework to life in Python 3? >  What I see is the chicken-and-egg problem endemic with Python 3: developers > wait

Re: [Web-SIG] PEP 444 / WSGI 2 Async

2011-01-06 Thread Jacob Kaplan-Moss
On Thu, Jan 6, 2011 at 7:47 PM, Alice Bevan–McGregor wrote: > All input is welcome; I do want to hear from both framework developers and > users of frameworks. OK, here's my input. I'm not comfortable speaking on behalf of the entire Django core team, but I am consciously wearing my Django BDFL h

[Web-SIG] Declaring PEP 3333 accepted (was: PEP 444 != WSGI 2.0)

2011-01-03 Thread Jacob Kaplan-Moss
On Sun, Jan 2, 2011 at 9:21 AM, Guido van Rossum wrote: > Although [PEP ] is still marked as draft, I personally think of it > as accepted; [...] What does it take to get PEP formally marked as accepted? Is there anything I can do to push that process forward? The lack of a WSGI answer

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

2010-10-22 Thread Jacob Kaplan-Moss
On Thu, Oct 21, 2010 at 6:35 PM, Graham Dumpleton wrote: > No other developers of actual web frameworks has commented at all on > PEP from what I can see. I wrote a bunch about WSGI/Py3 on python-dev: http://mail.python.org/pipermail/python-dev/2010-September/103674.html http://mail.python.