Replace django.utils.timezone.utc with datetime.timezone.utc #50
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Resolves openedx/public-engineering#356
Description
This PR addresses compatibility with Django 5.0 and above.
In Django 5.0, django.utils.timezone.utc has been removed as noted in the official release notes. To ensure forward compatibility—particularly with the upcoming upgrade to Django 5.2—this PR replaces usage of timezone.utc with
datetime.timezone.utcfrom Python’s standard library.This change prevents
AttributeErrorand ensures the codebase remains compatible with newer versions of Django.Release Notes Link:
https://docs.djangoproject.com/en/5.2/releases/5.0/#:~:text=django.utils.timezone.utc
Reference PR: rq/django-rq#610
Since django.utils.timezone.utc was merely an alias and has been removed in Django 5.0, replacing it with datetime.timezone.utc from the standard library is the recommended and compatible approach.