v0.14.0.a1

What's Changed

• #195: allow ASGIRequest in decompose() by @incidentist in #197
• [Snyk] Security upgrade ipython from 6.5.0 to 7.16.3 by @snyk-bot in #207
• #194: bump twilio version by @ReznikovRoman in #206
• django 4.0 by @jheld in #209

New Contributors

• @incidentist made their first contribution in #197
• @snyk-bot made their first contribution in #207
• @ReznikovRoman made their first contribution in #206

Full Changelog: v0.13.2...v0.14.0.a1

v0.13.1.b2

upgrades django dynamic fixture so the test suite (on django 3.1) passes again. removal of south docs/usage. correction of twilio python docs URL.

fixes issues:
#177
#178

v0.13.1.b1

#180 resolved via #181 #183 , but unfortunately tests are breaking due to a downstream package which will need a code change. Otherwise, this should work.

0.13.0.dev1

django 2.2 and 3.0 only. python 3.5 - 3.8

there is some code change #169 and documentation change #172 but otherwise this is business as usual in terms of firming up our compatibility story with django.

once testing/community feedback turns positive the next will likely be an rc1 (just to have an rc), and then assuming no additional code change, straight to 0.13.0.

0.12.1 Django 3 support

Whereas 0.12.0 had an installation issue, 0.12.1 is the same code except setup.py has been fixed.

For django 3.0 support, this is the base version.

0.12.0 Django 3 support (3.0 install issue, do not use).

This is on PyPI (currently), though it may be removed. It has an issue with the setup.py such that via setup.py django 3.0 cannot be installed.

0.12.1 is where you'll find the django 3.0 support via normal installation methods.

If you're on django 2.2 for instance, this will work fine, but again, not really the point of the upgrade :)

0.12.0rc1 Django 3 support

This implements #162 so we intend to support Django 3.0.

0.11.0

This release includes no effective code change (other than test & setup.py requirements).

We now have more explicit requirements against the django installation and the python installation.

We sort of still support python2, but that is more from laziness (not removing it's availability), than any technical reason to keep it around.

We now support django 2.2 officially. Any bugs against the django 2.x (2.2 specifically) will result in a version bump with the change. Mostly this means we are supporting django 2.2 with the versions of python that django 2.2 itself supports for python (we are following the compatibility matrix of django as well as we can).

0.11.0rc1

Includes release candidate support for django 2.2; once we're happy with the stability, we will fully release 0.11.0 (django 2.2 support).

0.10.0

This release does not include any code changes, but it does drop support for Django < 1.11, and tries to make more explicit 2.1 and python3.7 support.

Thank you to @km-pg for helping push python3.7 support in (which also allows 1.11.17+ support w/python3.7 usage with this project).