We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
see here: pandas-dev/pandas#5205
now going to be called __finalize__, and data is now _metadata. and going to called on pretty much everything before returning to the user.
__finalize__
_metadata
I am thinking about allowing this:
def __finalize__(self, other, method=None, **kwargs): ....
so that in theory a sub-class (as you guys have done), could dispatch on the method (if you need/want).
does this help?
The text was updated successfully, but these errors were encountered:
@jreback Thanks for the heads-up. That sounds useful, and a bit more like an official API; a lot like numpy's __array_finalize__, in fact.
__array_finalize__
Sorry, something went wrong.
yep thats where it is modeled from
should be merged in shortly
Closing, addressed in #49.
No branches or pull requests
see here: pandas-dev/pandas#5205
now going to be called
__finalize__
, and data is now_metadata
.and going to called on pretty much everything before returning to the user.
I am thinking about allowing this:
so that in theory a sub-class (as you guys have done), could dispatch on the method (if you need/want).
does this help?
The text was updated successfully, but these errors were encountered: