Added Django 1.10 support

[brunobord]

Review

This PR closes #203

• Tests (added in tox/circle-ci)
• CHANGELOG.rst Updated
• Delete your branch

[mgu]

LGTM, thanks.

[brunobord]

@mgu you misread. the tox.ini is wrong.

the tox.ini was wrong (see fixup)

[mgu]

you are right, I missed your copy/paste error

[brunobord]

dammit, something is wrong here:

tox -re django110-py27
[snip snip snip]
django110-py27 runtests: commands[1] | pip list --format=columns
Package                            Version    Location                                          
---------------------------------- ---------- --------------------------------------------------
appdirs                            1.4.3      
backports.shutil-get-terminal-size 1.0.0      
decorator                          4.0.11     
Django                             1.9.12     
[....]

[brunobord]

ok, got it, it was locked in the setup.py

[mgu]

LGTM 👍

[wo0dyn]

I would have set Django<1.11 here instead. Because, it'll install the very latest version of Django here if it's unpinned. What do you think?

[brunobord]

this silly requirement has almost make me lose my mind ; I was working with tox "django110" jobs, and it was still Django 1.9 that was installed. Luckily I did a careful check to the "pip freeze -l" that is executed during the job, or we could have a "fake" Django 1.10 support.

Maybe we could think about having a "latest" job, that installs the latest Django version, run it through a cron job (I don't know if circle-ci is able to do it, but travis does) and periodically check if the latest django release is compatible, in order to anticipate further releases.

[wo0dyn]

Maybe we could think about having a "latest" job, that installs the latest Django version, run it through a cron job (I don't know if circle-ci is able to do it, but travis does) and periodically check if the latest django release is compatible, in order to anticipate further releases.

Yeah, that would be awesome indeed.
Thanks for your explanation anyway.