[UPDATED] -- Upgraded django-db-mailer for Django 4.2+ compatibility by replacing deprecated imports and fields. #131
Conversation
This file contains hidden or 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
…replacing deprecated imports and fields.
- Included migration file to reflect changes made for Django 4.2+ compatibility. - Ensures database schema is consistent with the updated codebase.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Upgrade django-db-mailer for compatibility with Django 4.2+
ugettext_lazy()withgettext_lazy()in accordance with Django 4.2+ standards. Issue #130url()imports withre_path()fromdjango.urlsto ensure compatibility. Issue #130NullBooleanField()toBooleanField(null=True)in models to remove deprecated field usage. Issue #126This commit ensures the library continues to function with modern versions of Django while maintaining backward compatibility where possible.