On Thu, Jan 6, 2011 at 7:47 PM, Alice Bevan–McGregor <al...@gothcandy.com> 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 hat, and I do know that many (most?) of Django's core team feels as I do. And I'm feeling incredibly disheartened. Python 3 was released in December 2008. I assumed we'd have an updated WSGI spec wthin maybe 6 months. It's been two years, and we still don't have a WSGI spec. This fundamentally means that it's not worth my time to port Django to Python 3 -- the bits where Django meets WSGI are critical, and I simply can't get excited about targeting a moving spec with potential incompatible implementations. The lack of a WSGI-for-Py3 is a fundamental enthusiasm killer. Django is, at the end of the day, a framework designed to be deployed. Until I can do so, there's no use even starting the porting process. A few months ago, PJE posted PEP 3333. It looked good... and then nothing happened. I tried to prod things forward, and some more discussion ensued... and now it looks like it's stalling again. Each time, discussion of PEP 444 seems to derail discussion of PEP 3333. I have no skin in this game. Frankly, I have a huge amount of trouble following the discussions, and I can't speak to the technical merits of one over the other. But even if PEP 444 is a million times better than PEP 3333, 444 is clearly a *lot farther off. But PEP 444 seems to be where all the energy keeps ending up. At this rate, I really wonder if it'll be another two years before we have a working WSGI for Python 3. I hope I'm being pessimistic. Prove me wrong. Please. Can we please, please, PLEASE, pause discussion of PEP 444 until PEP 3333 is finalized? Jacob _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
