Drop pytz dependency in favor of Python's standard library timezone #612
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.
This PR removes the
pytz
dependency from django-dbbackup, aligning with Django's migration to Python's standard libraryzoneinfo
as the default timezone implementation since Django 4.0.Changes Made
pytz
from project dependencies inpyproject.toml
datetime.timezone.utc
instead ofpytz.utc
Background
Django 4.0 introduced
zoneinfo
as the default timezone implementation, moving away frompytz
. The django-dbbackup package was still carryingpytz
as a dependency despite only using it in a single test case for timezone-aware datetime testing.Impact
This change:
Testing
dbbackup.utils.timestamp()
works correctly withdatetime.timezone.utc
The
utils.timestamp()
function already uses Django's timezone utilities (django.utils.timezone
), so no changes were needed to the core functionality.Fixes #611.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.