TimeScoped.is_active: drop deprecated utcnow#197
Closed
c-tonneslan wants to merge 1 commit into
Closed
Conversation
datetime.utcnow() emits a DeprecationWarning on 3.12 and is slated for removal. The date is only used for an ISO-format comparison, so a timezone-aware now() works the same. Signed-off-by: Charlie Tonneslan <cst0520@gmail.com>
Author
|
Duplicate of the model change already in #194. Closing. |
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
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.
datetime.utcnow()warns under 3.12 and is on track for removal. Since the value is only used as an ISO date for string comparison, a timezone-awarenow(timezone.utc)works the same.