RemovedInDjango41Warning
See original GitHub issueGot this one today using Django 3.2.2:
RemovedInDjango41Warning: 'modeltranslation' defines default_app_config = 'modeltranslation.apps.ModeltranslationConfig'. Django now detects this configuration automatically. You can remove default_app_config.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
python - How to also ignore warnings in pytest about removal ...
Depending on your Django release, RemovedInDjango41Warning is a subclass of either DeprecationWarning (Django 4.0, still in development) or ...
Read more >RemovedInDjango41Warning for default_app_config in `__init ...
Django version 3.2.7 .../venv/lib/python3.8/site-packages/django/apps/registry.py:91: RemovedInDjango41Warning: 'drf_spectacular' defines ...
Read more >Fix RemovedInDjango41Warning about default_app_config
Coming soon: A brand new website interface for an even better experience!
Read more >Changelog — django-dbbackup 4.0.2 documentation
Fix RemovedInDjango41Warning related to default_app_config #413; Add authentication database support for MongoDB #379; Remove six dependency ...
Read more >Django 3.2 release notes
These release notes cover the new features, as well as some backwards incompatible changes you'll want to be aware of when upgrading from...
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
Should be fixed in v0.18.0.
Sure, people are already working on this: https://github.com/deschler/django-modeltranslation/pull/631
But we need to refactor
get_version
for setup.py before we can merge it.