On 16 September 2010 07:16, Terry Reedy <tjre...@udel.edu> wrote: >> I'm not working to get Django running on Python 3.1 because I don't >> feel confident I'll be able to put any apps I write into production. > > Why not? Since the I/O speed problem is fixed, I have no idea what you are > referring to. Please do be concrete.
At the risk of putting words into Jacob's mouth, I understood him to mean that "production quality" WSGI servers either do not exist, or do not implement a consistently defined spec (i.e., everyone is doing their own thing to adapt WSGI to Python 3). There is something of a chicken and egg situation here as with everywhere else (scientific users weren't moving until scipy did, lots of projects based round Twisted can't go until Twisted does, ...) but in the case of web/WSGI, there's a standard, defined in a PEP, with a reference implementation (wsgiref) in the stdlib. So the core has a greater interest. Personally, I don't write web applications (not even in Python :-)) so my interest is minimal. But I think the issue is real, and it's valid for the core team to be concerned. Whether I'd want to delay 3.2, I'm not so sure - certainly not indefinitely, there should be a "put up or shut up" deadline. But I'd be sad if Python 3 saw a reversion to the days of "Python isn't a good web development language because there's no standard infrastructure" comments that was the situation before WSGI existed... Paul. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
