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

ENH: Let event offsets be up to 12 hours. #1442

merged 1 commit into from Aug 30, 2016


None yet
3 participants

jbredeche commented Aug 29, 2016

We used to cap at 6.5 hours, but that's not enough for longer trading sessions like the CME.


This comment has been minimized.

coveralls commented Aug 29, 2016

Coverage Status

Coverage remained the same at 86.125% when pulling 749c2ee on schedule-all-the-hours into 0ae85eb on master.

@@ -24,6 +26,18 @@ class TestStatelessRulesCME(StatelessRulesTests, TestCase):
HALF_SESSION = pd.Timestamp("2014-07-04", tz='UTC')
FULL_SESSION = pd.Timestamp("2014-09-24", tz='UTC')
def test_far_after_open(self):
minute_groups = minutes_for_days(, ordered_days=True)

This comment has been minimized.


ehebert Aug 29, 2016


Does this mean we are testing every day in the calendar?

This comment has been minimized.


This comment has been minimized.


ehebert commented Aug 29, 2016

LGTM implementation wise; however had a question about the use of minutes_for_days in tests, with an eye on test duration.

@jbredeche jbredeche merged commit 7fe1a56 into master Aug 30, 2016

2 checks passed

continuous-integration/appveyor/pr AppVeyor build succeeded
continuous-integration/travis-ci/pr The Travis CI build passed

@jbredeche jbredeche deleted the schedule-all-the-hours branch Aug 30, 2016

bartosh pushed a commit to bartosh/zipline that referenced this pull request Sep 27, 2016

Merge pull request quantopian#1442 from quantopian/schedule-all-the-h…

ENH: Let event offsets be up to 12 hours.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment