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
The docs recommend Using each of TimeZones, CompoundPeriods, TimesDates, and Dates at various points. Can TimesDates stand alone or is it just an augmentation of Dates? My guess would be that it is an augmentation and full functionality requires both TimesDates and Dates but I could be wrong.
Conversely my reading would have me guess that I don't have to load TimeZones if I am uninterested in timezone support. (I happen to not be).
I'm not sure either way on CompoundPeriods.
Is there the potential to add a flexible parser ala DateFormat but compatible with the higher range of TimeDates?
I haven't actually used TimesDates yet but having found it now I hope to use it in the future to avoid having both Date and Time columns in a DataFrame since my Time values are 100microsecond resolution typically.
The text was updated successfully, but these errors were encountered:
The docs recommend Using each of TimeZones, CompoundPeriods, TimesDates, and Dates at various points. Can TimesDates stand alone or is it just an augmentation of Dates? My guess would be that it is an augmentation and full functionality requires both TimesDates and Dates but I could be wrong.
Conversely my reading would have me guess that I don't have to load TimeZones if I am uninterested in timezone support. (I happen to not be).
I'm not sure either way on CompoundPeriods.
Is there the potential to add a flexible parser ala DateFormat but compatible with the higher range of TimeDates?
I haven't actually used TimesDates yet but having found it now I hope to use it in the future to avoid having both Date and Time columns in a DataFrame since my Time values are 100microsecond resolution typically.
The text was updated successfully, but these errors were encountered: