I see a couple mentions in this thread of Flask taking a while to adopt Python 3. I am relatively new to Flask, could you explain why they are seemingly behind things in regards to Python 3?
Few core developers (mainly, one, Armin) that couldn't be bothered enough. It's a volunteer project after all.
He did write about the unicode problems with the Python 3 changes and the need for an improved WSGI spec (heck, he even co-wrote the unicode literal change PEP).
But after the new WSGI spec was out, and the u thing was already implemented in 3.3 pre-release, there was no much motion in Flask, whereas Pyramid, Django and others have already started work.
Even the "When will Flask support Python 3" document has not updated and is 2 years out of date in it's contents.
Comments
I see a couple mentions in this thread of Flask taking a while to adopt Python 3. I am relatively new to Flask, could you explain why they are seemingly behind things in regards to Python 3?
The Flask author's post about issues he has faced with Python 3 might give some insight to that: http://lucumr.pocoo.org/2011/12/7/thoughts-on-python3/
There is some work currently going on to make Flask run on Python 3.2.
https://github.com/puzzlet/flask/commits/py3-dev
Few core developers (mainly, one, Armin) that couldn't be bothered enough. It's a volunteer project after all.
He did write about the unicode problems with the Python 3 changes and the need for an improved WSGI spec (heck, he even co-wrote the unicode literal change PEP).
But after the new WSGI spec was out, and the u thing was already implemented in 3.3 pre-release, there was no much motion in Flask, whereas Pyramid, Django and others have already started work.
Even the "When will Flask support Python 3" document has not updated and is 2 years out of date in it's contents.