-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Custom Array Types Dropped on pd.Merge #23360
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
duplicate for #23020 there is a PR in the works |
@jreback thanks Jeff for letting me know. |
@TomAugspurger How did you account for this on cyberpandas? Just curious |
It's indeed different than #23020 (which is about merging on an EA columns). @achapkowski We already have tests in the |
@jorisvandenbossche They did when I created the extension array, let me re-run them and I'll get back to you today. |
@jorisvandenbossche Which BaseExtensionTests are you referring to? In v.23 there are no tests called |
I mean all the test that inherit from |
Code Sample, a copy-pastable example if possible
I have written a custom dtype and array for my own API.
When I do a
pd.merge
, the type reverts back toobject
notgeometry
.In cyberpandas, I do not see the same behavior. What needs to be set to accomplish this?
The text was updated successfully, but these errors were encountered: