-
Notifications
You must be signed in to change notification settings - Fork 915
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
BaseIndex
and IndexedFrame
has overlapping logics
#10068
Comments
This issue has been labeled |
Part of #10153 This PR refactors `filling.repeat` cython API to accept a list of columns instead of Frame object. In this PR I'm also trying out a possibly better pattern for index and indexed_frame to share logics, which might become a solution for #10068. Authors: - Michael Wang (https://github.com/isVoid) - Vyas Ramasubramani (https://github.com/vyasr) Approvers: - Vyas Ramasubramani (https://github.com/vyasr) URL: #10371
This issue has been labeled |
@charlesbluca @shwina I think this issue is basically stating what we discussed on a recent PR, the fact that we may eventually want a common parent class for |
One idea @vyasr and I discussed offline is for A |
From review comments: #9832 (review), recent python refactors #9832 #9807 has created some duplicate logics in
BaseIndex
andIndexedFrame
. The main diverging part of the implementation mostly lies in column selection (handling index columns and user inputs). For some methods (such as_apply_boolean_mask
), which unconditionally pass in all columns forindex
/indexed_frame
, we should be able to merge common code path while dispatching just the column selection part to each object to reduce code duplication.The text was updated successfully, but these errors were encountered: