3 ms·
http://www.python.org/dev/peps/pep-3333/ http://www.python.org/dev/peps/pep-3333/ Last-Modified: 2011-01-16 09:57:25 +0000 (Sun, 16 Jan 2011) ... Status: Final
by tbatterii 14y ago
http://www.python.org/dev/peps/pep-3333/ http://www.python.org/dev/peps/pep-3333/
Last-Modified: 2011-01-16 09:57:25 +0000 (Sun, 16 Jan 2011)
...
Status: Final
...
Created: 26-Sep-2010
Until this was made final(January 2011), web frameworks that use the wsgi spec had no python 3 path short of ditching the wsgi spec.
Now that it is final, there is a path to python 3 for web-dev. Cherrpy got there first I think. Pyramid/Webob got there, and others as well, and I'm sure Django will get there soon enough.
I'd say web-dev adoption of python 3 has been pretty swift.
- maaku 14y agoDjango has unofficially supported python 3 for a year.
- bobwaycott 14y agoWasn't experimental support only announced just over a month ago? https://www.djangoproject.com/weblog/2012/aug/19/experimental-python-3-support/ https://www.djangoproject.com/weblog/2012/aug/19/experimenta...
- takluyver 14y agoThere were unofficial versions of Django (forks, but not in the hostile sense) ported to Python 3 before that. The announcement marks the work being done in the main Django codebase, meaning that the next release will work on Python 3.
- tbatterii 14y agoso, for about as long as pep 3333 has been approved. that was my point. No web framework that uses wsgi(pretty much all of them) were going to move to python 3.X without it.