uploader: make util_test py3-compatible internally
#3179
Merged
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
Summary: Follow-up to #2978, which added explicit configuration of `TZ=UTC`. In cPython 3, the time zone used by `datetime.datetime.fromtimestamp` is [cached when `time` is imported][1] unless explicitly reset, so mocking the environment variable is no longer sufficient. We now call `tzset` ourselves; we could also just set `TZ=UTC` before importing `datetime`, but this seems cleaner. [1]: https://github.com/python/cpython/blob/2528a6c3d0660c03ae43d796628462ccf8e58190/Modules/timemodule.c#L1752-L1763 Test Plan: A test sync shows that this test passes in both Python 2 and Python 3, whereas it previously only passed in Python 2. wchargin-branch: util-test-tzset
bileschi
pushed a commit
to bileschi/tensorboard
that referenced
this pull request
Mar 3, 2020
Summary: Follow-up to tensorflow#2978, which added explicit configuration of `TZ=UTC`. In cPython 3, the time zone used by `datetime.datetime.fromtimestamp` is [cached when `time` is imported][1] unless explicitly reset, so mocking the environment variable is no longer sufficient. We now call `tzset` ourselves; we could also just set `TZ=UTC` before importing `datetime`, but this seems cleaner. [1]: https://github.com/python/cpython/blob/2528a6c3d0660c03ae43d796628462ccf8e58190/Modules/timemodule.c#L1752-L1763 Test Plan: A test sync shows that this test passes in both Python 2 and Python 3, whereas it previously only passed in Python 2. wchargin-branch: util-test-tzset
Merged
nfelt
pushed a commit
that referenced
this pull request
Mar 4, 2020
Summary: Follow-up to #2978, which added explicit configuration of `TZ=UTC`. In cPython 3, the time zone used by `datetime.datetime.fromtimestamp` is [cached when `time` is imported][1] unless explicitly reset, so mocking the environment variable is no longer sufficient. We now call `tzset` ourselves; we could also just set `TZ=UTC` before importing `datetime`, but this seems cleaner. [1]: https://github.com/python/cpython/blob/2528a6c3d0660c03ae43d796628462ccf8e58190/Modules/timemodule.c#L1752-L1763 Test Plan: A test sync shows that this test passes in both Python 2 and Python 3, whereas it previously only passed in Python 2. wchargin-branch: util-test-tzset
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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:
Follow-up to #2978, which added explicit configuration of
TZ=UTC. IncPython 3, the time zone used by
datetime.datetime.fromtimestampiscached when
timeis imported unless explicitly reset, so mockingthe environment variable is no longer sufficient. We now call
tzsetourselves; we could also just set
TZ=UTCbefore importingdatetime,but this seems cleaner.
Test Plan:
A test sync shows that this test passes in both Python 2 and Python 3,
whereas it previously only passed in Python 2.
wchargin-branch: util-test-tzset