fix: Replace ugettext_lazy with gettext_lazy for compatibility with n… #4
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
…ewer versions of Django
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.
Subject: [Pull Request] Fix compatibility issue with latest Django version
Dear @mikebader ,
I am writing to inform you that I have submitted a pull request to address the compatibility issue with the latest Django version in the django-vitae project.
The issue was caused by the use of ugettext_lazy instead of gettext_lazy, which caused a failure when running tests. I have corrected this issue and tested the changes to ensure that they are working properly.
I believe that my changes will enable the django-vitae project to be used with the latest version of Django, and I hope that you will find them useful.
Thank you for your time and consideration.
Sincerely,