It builds on the py3_work2 branch, fixes a lot of stuff, and adds from __future__ import unicode_literals everywhere to make it easier to support both versions. There's also a commit to remove usage of str() as much as possible (and useful) because it has a different output in Python 2 and 3 when bytes are given.
Finally, I've added a tox.ini file so you can run tox and it will run the unit tests (and flake8) on the combination of the following environments:
- python 2.7, 3.4, 3.5, and 3.6
- flask 0.11 and 0.12
This will, of course, take a long time. But you can select a subset of the environments with tox -e py34-flask011. Refer to the tox docs for more info.
Of course I'll need to update this PR each time a new commit lands in master, so feel free to ask me to rebase, and let's not wait too long if possible ;-)
For future developments, I recommend reading http://python-future.org/compatible_idioms.html (event if it's geared towards future and not six, that we currently use).
OK that's a big one :-)
It builds on the py3_work2 branch, fixes a lot of stuff, and adds
from __future__ import unicode_literalseverywhere to make it easier to support both versions. There's also a commit to remove usage ofstr()as much as possible (and useful) because it has a different output in Python 2 and 3 when bytes are given.Finally, I've added a
tox.inifile so you can runtoxand it will run the unit tests (and flake8) on the combination of the following environments:- python 2.7, 3.4, 3.5, and 3.6
- flask 0.11 and 0.12
This will, of course, take a long time. But you can select a subset of the environments with
tox -e py34-flask011. Refer to the tox docs for more info.Of course I'll need to update this PR each time a new commit lands in master, so feel free to ask me to rebase, and let's not wait too long if possible ;-)
For future developments, I recommend reading http://python-future.org/compatible_idioms.html (event if it's geared towards
futureand notsix, that we currently use).