-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
[MRG] FIX #10561: more tolerance in float equality for 0 bandwidth #13130
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
Conversation
Open to review so that we can have this fixed for 0.20.3 |
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.
LGTM but I think we are encouraging using assert np.allclose
now?
I don't think this is a hard convention.
allclose is no different when comparing to 0. I chose the function already
used in the file
|
And assert_allclose, or assert np.allclose? I think they have different
defaults and different error messages
|
yeah they have different defaults... I don't know actually. I'll open an issue and ask |
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.
LGTM!
…learn#13130)" This reverts commit e260583.
…learn#13130)" This reverts commit e260583.
The test was new in 0.20, hence the new failure on some Debian platforms