Use ZoneInfo as primary source of timezone data #8924
Merged
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.
Note: Before submitting this pull request, please review our contributing guidelines.
Description
This PRs switches over to
ZoneInfo
as the primary source of timezone data in DRF. This PR accomplishes several things:pytz
.pytz
functionality over toZoneInfo
.ZoneInfo
timezones. This is because unlikepytz
, error checking has to be done more or less manually in able to determine ambiguous and imaginary timezones (see this doc on migrating toZoneInfo
). We previously had exception handling inDateTimeField
forpytz
errors, but I added manually checking that will coverZoneInfo
timezones.Django will provide us
ZoneInfo
instances as long asUSE_DEPRECATED_PYTZ
is not enabledFixes #8577