Deleted unnecessary default_app_config settings starting with django3.2 #196
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LeeHanYeong
changed the title
LeeHanYeong
force-pushed
the
feat/django4
branch
from
ace450c
to
7bbd64d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Warning problem solving
python3.9/site-packages/django/apps/registry.py:91: RemovedInDjango41Warning: 'versatileimagefield' defines default_app_config = 'versatileimagefield.apps.VersatileImageFieldConfig'. Django now detects this configuration automatically. You can remove default_app_config.