Django-twilio

Latest version: v0.14.3.3

Safety actively analyzes 623490 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 6

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).

0.9.3

General Notes
This is similar to 0.9.2, but there was a mistake in the requirements.txt where django 2.1 was not explicitly allowed!

Community Contributions
tim-schilling for fixing the requirements.txt

0.9.2

Support for python 3.7 and django 2.1

0.9.1

General Notes

Version 0.9.1 improves some documentation changes against twilio 6.x SDK.

It also includes a fix to the django admin site on the test project, if that is used (common for small dev and debug local testing).


Community Contributions
DoomPatrol thank you for adding the improved documentation

Backwards Incompatibilities

Python 3.3 is no longer part of the travis test suite due to pip dropping support for it. We have not technically dropped support for it, but will be no longer running explicit tests against it, and thus it would be wise to test internally on your project going forward. So, consider this a pending deprecation warning. This should only affect users of django 1.8.

Thank you all!

Page 4 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.