-
Notifications
You must be signed in to change notification settings - Fork 667
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
Add deprecation warning for memoryreader inclusive indexing in timeseries. #3894
Add deprecation warning for memoryreader inclusive indexing in timeseries. #3894
Conversation
Codecov ReportBase: 94.35% // Head: 94.35% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #3894 +/- ##
========================================
Coverage 94.35% 94.35%
========================================
Files 194 194
Lines 25064 25066 +2
Branches 3391 3392 +1
========================================
+ Hits 23649 23651 +2
Misses 1366 1366
Partials 49 49
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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.
I suggest to make the warning more specific and we need
- test
- entry in CHANGELOG under Deprecations
- doc entry for deprecation (under
stop
keyword)
@@ -515,6 +515,10 @@ def timeseries(self, asel=None, start=0, stop=-1, step=1, order='afc'): | |||
.. versionchanged:: 1.0.0 | |||
Deprecated `format` keyword has been removed. Use `order` instead. | |||
""" | |||
warnings.warn("MemoryReader.timeseries inclusive `start` and `stop`" |
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.
Can we do the warning only if stop
is changed and not the default?
The warning should only be about start
becoming exclusive instead of inclusive.
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.
@orbeckst can warn only if stop is set.
I assume you mean stop rather than start in "The warning should only be about start becoming exclusive instead of inclusive"?
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.
Yes, you’re right, of course. Sorry for the typo.
Co-authored-by: Irfan Alibay <IAlibay@users.noreply.github.com>
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.
See edit: oops I started writing here then wrote the specific comment
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.
lgtm
(just applying suggestions)
Co-authored-by: Irfan Alibay <IAlibay@users.noreply.github.com>
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.
lgtm assuming CI comes back green
Related to #3893
Changes made in this Pull Request:
PR Checklist