-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Some cleanups of merge_asof tests and error code #26249
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
There's a fifth potential cleanup. Currently, most of the tests use the "ticker data" example with a I see potentially two options here:
What do you think? If option 2 sounds good, now would be a good time for me to do it at least, given that I've been looking at that code lately (because I've been doing asof merges on dataframes that contain a lot of categorical data). |
Maybe this would also be a good first step to then work on #16454? |
I like option 2, as it's more comprehensive. |
@gfyoung Me too, especially since I'm interested in having merge_asof() working better with categorical data. Just looking for some approval that this direction is good with the Pandas developers before reworking a bunch of the tests there., and also that it's okay to use the more advanced pytest features in tests for Pandas. |
@chrish42 I'd say go for it! We use purest parametrized fixtures in other places as well so nothing out of the ordinary |
I think this has been cleaned up over the years so closing. Can open individual tickets for remaining issues is something isnt addressed |
This is a follow-up to #26242, for the following points:
test_merge_asof.py
that checks thatmerge_asof()
raises an exception if called on unordered categories for a merge key.test_merge_asof.py
merge_asof
works when one of the merge keys is an ordered categoricalrepr(x.dtype)
instead ofx.dtype
as input to.format()
in exception messages everywhere in merge.pyThe text was updated successfully, but these errors were encountered: