-
Notifications
You must be signed in to change notification settings - Fork 736
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
RFC: zebras.TimeFrame. #2644
base: dev
Are you sure you want to change the base?
RFC: zebras.TimeFrame. #2644
Conversation
Both classes have easy to use constructors in ``zebras.time_frame`` and | ||
``zebras.split_frame``. | ||
|
||
## Discussion |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about missing values?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing values can be handled within TimeFrame
by adding another column to it. I don't think we need to add a special case for this.
* We can implement custom behaviour such as ``.split`` easily on ``TimeFrame``. | ||
* ``SplitFrame`` has a notion of past and future. | ||
|
||
## Obstacles |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree, this seems a big change and gain should outweigh the effort.
Rendered
Started implementation in #2609
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup