orbit-oss/flask
4
4
Fork 2
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update information about Python 3

Browse source 
Python 3 and Flask is a good combination nowadays that works rather well. In fact, [most PyPI libs](https://regebro.wordpress.com/2014/10/23/59-of-maintained-packages-support-python-3/) are now ported and it's generally ok to encourage people to use Python 3 for new projects.
This commit is contained in:
Sven-Hendrik Haase 2014-12-02 18:13:02 +01:00
parent 924763afd1
commit 83336e0622
1 changed files with 3 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

24
docs/python3.rst
View file

@ -30,30 +30,12 @@ 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.
Few Users
---------
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.
Unless you require absolute compatibility, you should be fine with Python 3
nowadays. Most libraries and Flask extensions have been ported by now and
using Flask with Python 3 is a stable affair.
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