changed to gettext_lazy because of deprecation #5
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
|
Any chance this PR could be merged, assuming it's acceptable? Django 4.0 is nearly here and it would be good to know this nice app will keep working :) Thank you. |
|
I'll try to release new version this week, Thanks. |
|
Took me way longer than promised, but it's finally released |
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.
There is a deprecation hint since Django 3.0 for the usage of ugettext_lazy as seen here https://docs.djangoproject.com/en/3.0/releases/3.0/#id3
Replacing them with the gettext counterpart should be done.