You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should a lead_symbol = "all" option be introduced to evalute the period against a composite of all underlying calendars as opposed to a specific calendar?
The period would be evaluated such that:
start and end evaluate to sessions/times of the composite calendar.
durations are evaluated against the minutes / sessions of the composite calendar.
Please 👍 this comment if you would find this option useful.
Without giving it too much thought, might require:
Could an option be added to existing daterange.Getter_ subclasses to work off a calendar_utils.CompositeCalendar? Or would it be necessary to define dedicated GetterCompDaily and GetterCompIntraday classes?
This discussion was converted from issue #10 on May 19, 2022 12:20.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Should a
lead_symbol = "all"
option be introduced to evalute the period against a composite of all underlying calendars as opposed to a specific calendar?The period would be evaluated such that:
start
andend
evaluate to sessions/times of the composite calendar.Please 👍 this comment if you would find this option useful.
Without giving it too much thought, might require:
daterange.Getter_
subclasses to work off acalendar_utils.CompositeCalendar
? Or would it be necessary to define dedicatedGetterCompDaily
andGetterCompIntraday
classes?Would definiitely require:
Beta Was this translation helpful? Give feedback.
All reactions