django >=2.2, <=3.1 (drops 1.11)

[n2ygk]

Fixes #822, #803

Description of the Change

Remove Django 1.11 from and add Django 3.1 to test matrix, setup.py

Checklist

• PR only contains one change (considered splitting up PR)
• unit-test added
• documentation updated
• CHANGELOG.md updated (only for user relevant changes)
• author name in AUTHORS

[n2ygk]

ugh, forgot that .travis.yml separately lists the environents.

[codecov]

Codecov Report

Merging #823 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #823   +/-   ##
=======================================
  Coverage   97.08%   97.08%           
=======================================
  Files          58       58           
  Lines        3158     3158           
=======================================
  Hits         3066     3066           
  Misses         92       92           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7458d56...dc8adfa. Read the comment docs.

[sliverc]

Thanks for looking out for this. I think we should wait with this PR though as DRF 3.11 is not officially supporting Django 3.1. Also locally on my machine the tests are failing with DRF 3.11 and Django 3.1. Reason seems that the setup.py is not updated yet in terms of Django range and Travis actually doesn't install Django 3.1 but still 3.0.

See for example this job

[n2ygk]

OK, I've updated setup.py to add py38, and django<3.2. Let's see if that at least fixes the travis job.

[n2ygk]

@sliverc FYI - I've opened encode/django-rest-framework#7518 as it does appear that Django 3.1 is supported as of DRF 3.11.1 but the documentation is lagging.

[sliverc]

It was quicker to create a new PR #835 instead of updating this. Superseded therefore.