Use tz.UTC in favor of tz.tzutc() where possible. #910
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
To allow the UTC object to be accessible from the functions in `dateutil.tz.tz` such as `gettz` and datetime_exists, it is necessary to define the UTC constant here and import it into `dateutil.tz`. This is a very minor performance improvement, avoiding a call to the `tzutc()` constructor.
Merged
This was referenced Mar 11, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary of changes
In version 2.7.0, we added the
tz.UTCobject as a convenience accessor for thetzutcsingleton. This PR goes updates other modules and tests that were usingtzutc()to usetz.UTC, except where it doesn't make sense to do so.Pull Request Checklist