-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
BUG: pytz.AmbiguousTimeError not caught in hypothesis test test_on_offset_implementations (GH41906) #41907
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: pytz.AmbiguousTimeError not caught in hypothesis test test_on_offset_implementations (GH41906) #41907
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment otherwise LGTM
f97e9a4
to
d914467
Compare
is it possible to add the offending test case? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it possible add the offending test case as well?
Sure, any preference between 1) a separate test with |
prefer 1 |
def test_nontick_offset_with_ambiguous_time_error(case): | ||
# .apply for non-Tick offsets throws AmbiguousTimeError when the target dt | ||
# is dst-ambiguous | ||
original_dt, target_dt, offset, tz = case |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you make these parameterized arguments instead? i.e.
def test_nontick_offset_with_ambiguous_time_error(original_dt, target_dt, offset, tz):
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no problem
ff590be
to
fedb49e
Compare
I took at a quick look at the failing
Are you okay with removing this original offending test case in |
@jackzyliu yeah go ahead and skip for py37 (going to merge this to 1.4 which is going to have 3.7 removed anyhow), so just xfail for rn. |
…fset_implementations (GH41906)
fedb49e
to
25f1368
Compare
@jreback Got it! Just updated it accordingly and rebased after master. |
thanks @jackzyliu |
…fset_implementations (GH41906) (pandas-dev#41907)
…fset_implementations (GH41906) (pandas-dev#41907)
test_on_offset_implementations
#41906