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

Merge pull request #1264 from svenstaro/patch-1

Browse source 
Update information about Python 3
This commit is contained in:
Markus Unterwaditzer 2014-12-04 22:36:31 +01:00
commit 86525d9b37
1 changed files with 8 additions and 36 deletions
Download patch file Download diff file Expand all files Collapse all files

44
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,35 +20,12 @@ 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 Unless you require absolute compatibility, you should be fine with Python 3
details as it was written before WSGI was updated to Python 3. While the nowadays. Most libraries and Flask extensions have been ported by now and
API for Werkzeug and Flask on Python 2.x should not change much we cannot using Flask with Python 3 is generally a smooth ride. However, keep in mind
guarantee that this won't happen on Python 3. that most libraries (including Werkzeug and Flask) might not quite as stable
on Python 3 yet. You might therefore sometimes run into bugs that are
Few Users usually encoding-related.
---------
Although moving to Python 3 should be done someday, most people still use
Python 2 for now. As a result many of the problems you will encounter are
probably hard to search for on the internet if they are Python 3 specific.
Small Ecosystem
---------------
Some Flask extensions, documentation and PyPI provided libraries do not
support Python 3 yet.
Even if you start your project with knowing that all you will need is
supported by Python 3 you don't know what happens six months from now.
But if you are familiar with Python 3 and Flask extension, you can start
porting libraries on your own.
Recommendations
---------------
Unless you are already familiar with the differences in the versions we
recommend sticking to current versions of Python until the ecosystem
caught up.
The majority of the upgrade pain is in the lower-level libararies like The majority of the upgrade pain is in the lower-level libararies like
Flask and Werkzeug and not in the actual high-level application code. For Flask and Werkzeug and not in the actual high-level application code. For