maya-chen/flask
1
0
Fork 0
forked from orbit-oss/flask
Code Pull requests Activity

Remove head lines and add versions of first Python 3 support

Browse source
This commit is contained in:
Sven-Hendrik Haase 2014-12-02 21:09:45 +01:00
parent eb6df3ddf1
commit a5d24ac0d9
1 changed files with 2 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

17
docs/python3.rst
View file

@ -7,17 +7,12 @@ Flask and all of its dependencies support Python 3 so you can in theory
start working on it already. There are however a few things you should be start working on it already. There are however a few things you should be
aware of before you start using Python 3 for your next project. aware of before you start using Python 3 for your next project.
Requirements
------------
If you want to use Flask with Python 3 you will need to use Python 3.3 or If you want to use Flask with Python 3 you will need to use Python 3.3 or
higher. 3.2 and older are *not* supported. higher. 3.2 and older are *not* supported.
In addition to that you need to use the latest and greatest versions of In addition to that you need to use the latest and greatest versions of
`itsdangerous`, `Jinja2` and `Werkzeug`. `itsdangerous`, `Jinja2` and `Werkzeug`. Flask 0.10 and Werkzeug 0.9 were
the first versions to introduce Python 3 support.
API Stability
-------------
Some of the decisions made in regards to unicode and byte utilization on Some of the decisions made in regards to unicode and byte utilization on
Python 3 make it hard to write low level code. This mainly affects WSGI Python 3 make it hard to write low level code. This mainly affects WSGI
@ -25,14 +20,6 @@ middlewares and interacting with the WSGI provided information. Werkzeug
wraps all that information in high-level helpers but some of those were wraps all that information in high-level helpers but some of those were
specifically added for the Python 3 support and are quite new. specifically added for the Python 3 support and are quite new.
A lot of the documentation out there on using WSGI leaves out those
details as it was written before WSGI was updated to Python 3. While the
API for Werkzeug and Flask on Python 2.x should not change much we cannot
guarantee that this won't happen on Python 3.
Recommendations
---------------
Unless you require absolute compatibility, you should be fine with Python 3 Unless you require absolute compatibility, you should be fine with Python 3
nowadays. Most libraries and Flask extensions have been ported by now and nowadays. Most libraries and Flask extensions have been ported by now and
using Flask with Python 3 is generally a smooth ride. However, keep in mind using Flask with Python 3 is generally a smooth ride. However, keep in mind