Add support for Django 2.2
See original GitHub issueIs there a reason this is limited to Django<2.1
Also, the related django-migration-linter
tests for django_add_default_value
, and it doesn’t have that same limitation…
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Django 2.2 release notes
Django 2.2 is designated as a long-term support release. It will receive security updates for at least three years after its release. Support...
Read more >Adding support for Django 2.2 LTS to django-cms 4.0 #6790
Checklist · I have opened this pull request against release/4.0.x · I have updated the CHANGELOG.rst · I have added or modified the...
Read more >django-coverage-plugin - PyPI
A coverage.py plugin to measure test coverage of Django templates. Supported on: Python: 3.7 through 3.11. Django: 1.11, 2.x, 3.x and 4.x. Coverage.py:...
Read more >Changelog — django-statici18n 2.3.1 documentation
v1.9.0 (2020 Jan 11)¶ · [PR#48] Update django-appconf, thanks @zetaab · Add Django 2.2 support · Add Django 3.0 support · Drop Python...
Read more >Django REST framework: Home
Django (2.2, 3.0, 3.1, 3.2, 4.0, 4.1). We highly recommend and only officially support the latest patch release of each Python and Django...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Is this a platform issue? If so I would recommend using https://hub.docker.com/_/microsoft-mssql-server which should run on Unix systems as well.
Maybe even create a guide in the README to showcase to test the different database providers.
@yisraell okay. Then let’s wait a bit until s.o. can test. We will probably soon (1-2 months?) switch to Django 2.2, then I could do the testing.