Fix pendulum.test to properly unwind after an exception#445
Merged
sdispater merged 1 commit intopython-pendulum:masterfrom Mar 6, 2020
Merged
Fix pendulum.test to properly unwind after an exception#445sdispater merged 1 commit intopython-pendulum:masterfrom
sdispater merged 1 commit intopython-pendulum:masterfrom
Conversation
Previously, if an exception occurred inside a 'with pendulum.test(...)' block, then the monkeypatch would remain in place instead of being un-done. This could cause confusing results, as one failing test could cause other tests to run with an unexpected mock in place and cause other failures.
2c11502 to
0b4f34e
Compare
Contributor
Author
|
All the test failures appear to be unrelated. |
Collaborator
|
Thanks! |
Merged
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
2 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.
Previously, if an exception occurred inside a 'with pendulum.test(...)'
block, then the monkeypatch would remain in place instead of being
un-done. This could cause confusing results, as one failing test could
cause other tests to run with an unexpected mock in place and cause
other failures.