Python 3.2 support required

[kyegupov]

Python version 3.2 finally resolves the long-standing issue of Unicode support in WSGI headers (PEP 3333). Thus, it is now possible (and desirable) to port Werkzeug to Python 3 and embrace the future.

See also: http://docs.python.org/dev/whatsnew/3.2.html

[mitsuhiko]

It's on the roadmap, but there are more important issues right now that need to be tackled first. The next upcoming release will already clean up the internal implementation to ease the transition to Python 3.

[shon]

+1

[msabramo]

See #192 for some baby steps towards Python 3

[DasIch]

3.3 is now supported. 3.2 isn't and won't be supported.

[jayvdb]

It would be nice to clearly state that 3.2 wont ever be supported, in a front page somewhere.

I see http://werkzeug.pocoo.org/ says "Supports Python 2.6, 2.7 and 3.3." , which should be "Supports Python 2.6, 2.7 and 3.3+."

And maybe explicitly fail on cpython 3.2 during setup.py by using u'...' in setup.py .. as I believe that is the main problem with supporting 3.2 - all u'...' would need to be removed (and unicode_literals added), which is a lot of churn for little benefit.

[untitaker]

@jayvdb This will be resolved in the upcoming rewrite of the websites for Werkzeug/Flask/Jinja.