Raise our own utcnow
DeprecationWarning
with the right stacklevel
#486
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.
Previously, when time is mocked, no
DeprecationWarning
would be reported at all, and when time is not mocked, the originaldatetime.utcnow
would misattribute its reportedDeprecationWarning
to the code oftime_machine
itself. Fix both cases to attribute theDeprecationWarning
to the user code that calledutcnow
, by raising it ourselves with the rightstacklevel
, and test that we did so correctly.