Skip to content

Conversation

@drculhane
Copy link
Contributor

@drculhane drculhane commented Dec 19, 2025

Closes #5132. Closes #5149.

  • The binops in pdarrayclass.py now give a RuntimeWarning or a Floating Point Error (or nothing) if / or // cause a divide-by-zero, depending on the "divide" setting of ak.errstate.

  • Because the RuntimeWarning surfaced an issue in arctan2, I've rewritten that function somewhat. It now has an "out" parameter matching numpy, and uses the "where" parameter correctly.

  • Most of the original arctan2 function remains as _arctan2_, because (subjective opinion here) I think that calling it as a separate function improves the readability of the code.

  • In doing this rewriting, I removed some mypy ignores that are no longer needed.

  • I rewrote the unit tests for arctan2 to use our newer assert functions. I think this cleans up that code significantly. In the cases that use "where," I check both the returned result, and the returned "out" pdarray, since they should match.

Update:

Since other tests were also causing divide-by-zero errors, I extended the divide-by-zero check to use ak.errstate. I also bypassed additional tests in datetime once a divide-by-zero occurred, because they would also cause errors.

Copy link
Contributor

@ajpotts ajpotts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work!

@Bears-R-Us Bears-R-Us deleted a comment from codecov-commenter Jan 12, 2026
@drculhane
Copy link
Contributor Author

This could not be rebased, so it's been closed and replaced with PR #5315.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ak.arctan2 uses the "where" parameter incorrectly. floor division by zero doesn't match numpy

2 participants