What would it take to get Flask up and running with Python 3? I heard you got Jinja2 up and running on py3k but I am less sure about Werkzeug and the WSGI spec in general for Python 3. Have you put any thought into it or had any luck trying to accomplish it?
Not started yet. I have a talk at djangocon.eu about that topic and I will collect some experiences from other people there. After that, I might start porting.
Lovely. I have experience writing applications that are both py2 and py3 compatible. Flask seems like an easy app to port over, it is just werkzeug (and even WSGI in general) that seems like the bottleneck. Let me know once you have a gameplan for porting and I will be more than willing to help.
Now that PEP3333 and Python 3.2 are out, what are the plans for this?
Maybe a topic for sprinting at pycon or some work for google summer of code. Who knows ;)
Any developments on this idea?
If people want to work on it, go ahead. Currently our focus is more on making Flask/Werkzeug/Jinja2 work better with PyPy than Python 3 since this is what we consider a more reasonable platform for the next years. That being said, I don't have anything against a Python 3 version and we're refactoring code to make porting easier.
Okay. Do you think a ROADMAP file would be helpful in this scenario?
There's WIP in porting Werkzeug to Python 3, but many decisions regarding Unicode vs. Bytestrings have yet to be made. Also all commits need to be closely reviewed, because with a freshly ported, unstable testsuite, it's very easy to make errors.
(This is just what i comprehended. Feel free to correct me @RonnyPfannschmidt)
Flask now supports 3.3