-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
assert_*_equal issues #25135
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
Comments
|
I was not sure about how to use If that's not a public function, then please ignore this issue. Nevertheless, I think a public function on par with the numpy allclose would be very useful (with the ability to combine absolute and relative errors). |
That function is not public - but it does look like the return statements are redundant so will keep this open as a code cleanup issue. Also would take that improvement to the docstring. |
@chris-b1 if I understand this correctly, the assertions part ( |
The function
assert_almost_equal
may return the return value of another functions likeassert_frame_equal
orassert_series_equal
.But
assert_frame_equal
does not return any value explicitly, hence it shall always return None.Also,
assert_series_equal
may or may not return a value explicitly.Are those assertion functions usable or am I overlooking something?
The text was updated successfully, but these errors were encountered: