Django 3.2 compatibility
See original GitHub issueUsing the latest summernote (django-summernote==0.8.11.6) version results in some warnings:
/usr/local/lib/python3.9/site-packages/django_summernote/urls.py:8: RemovedInDjango40Warning: django.conf.urls.url() is deprecated in favor of django.urls.re_path()
and
/usr/local/lib/python3.9/site-packages/django/apps/registry.py:91: RemovedInDjango41Warning: 'django_summernote' defines default_app_config = 'django_summernote.apps.DjangoSummernoteConfig'. Django now detects this configuration automatically. You can remove default_app_config.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Download Django
The last version to support Python 2.7 is Django 1.11 LTS. ... These releases will be 100% compatible with the associated feature release,...
Read more >What's new in Django 3.2 LTS - TheOrangeOne
It's still worth noting that not everything in Django is async-compatible, like the ORM and caching layers. Instead, these are automatically ...
Read more >Django - endoflife.date
These releases will be 100% compatible with the associated feature release, unless this is impossible for security reasons or to prevent data loss....
Read more >A Django Upgrade Guide for Major and Minor Releases
With the upcoming Django 3.2 release in mind, this post goes through ... These releases will be 100% compatible with the associated feature...
Read more >Is postgres 14 compatible with Django3.2.3 and Django ...
I checked and Postgress 14.2 is compatible with the following. Django Rest Framework 3.12.4; Python version 3.9; Django version 3.2.3 ...
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
The DEFAULT_AUTO_FIELD warning should be fixed in your own application settings, AFAIK.
@lqez Do you plan to publish a new release soon?
Indeed, thanks.