Remove usages of datetime.utcfromtimestamp #7102
Merged
Conversation
This file contains 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
It's been deprecated in 3.12, and `fromtimestamp` is easier to use anyway. In addition, drop the pytz dependency, since the UTC time zone is available in the standard library.
SpecLad
force-pushed
the
rm-utcfromtimestamp
branch
from
344a2e8
to
621164c
Compare
Codecov Report
@@ Coverage Diff @@
## develop #7102 +/- ##
===========================================
- Coverage 82.43% 82.37% -0.06%
===========================================
Files 361 362 +1
Lines 39310 39398 +88
Branches 3591 3592 +1
===========================================
+ Hits 32405 32454 +49
- Misses 6905 6944 +39
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation and context
It's been deprecated in 3.12, and
fromtimestampis easier to use anyway.In addition, drop the pytz dependency, since the UTC time zone is available in the standard library.
How has this been tested?
Checklist
developbranch[ ] I have created a changelog fragment[ ] I have updated the documentation accordingly[ ] I have added tests to cover my changes[ ] I have linked related issues (see GitHub docs)[ ] I have increased versions of npm packages if it is necessary(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)
License
Feel free to contact the maintainers if that's a concern.