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
This may be a departure from strict IDL compatibility, but it would be useful if timespan() had more flexible time specification options:
Allow common abbreviations for time units -- currently only "days",. "hours", "minutes" and "seconds" are recognized. It would
be easy to also recognize "day", "d", "second", "secs",. "sec", "s", etc. as synonyms
Allow specification of a time range as an array (of strings, floats, np.datetimes, python datetimes), rather than just start time and duration
Allow for resetting the timespan, as if it had never been called
The text was updated successfully, but these errors were encountered:
This may be a departure from strict IDL compatibility, but it would be useful if timespan() had more flexible time specification options:
Allow common abbreviations for time units -- currently only "days",. "hours", "minutes" and "seconds" are recognized. It would
be easy to also recognize "day", "d", "second", "secs",. "sec", "s", etc. as synonyms
Allow specification of a time range as an array (of strings, floats, np.datetimes, python datetimes), rather than just start time and duration
Allow for resetting the timespan, as if it had never been called
The text was updated successfully, but these errors were encountered: