Skip to content
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

A few questions that could be clarified in the Docs #20

Open
jordancluts opened this issue Mar 27, 2020 · 1 comment
Open

A few questions that could be clarified in the Docs #20

jordancluts opened this issue Mar 27, 2020 · 1 comment

Comments

@jordancluts
Copy link

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.

@jordancluts
Copy link
Author

Just wanted to follow up that I'm really happy to have found this package and that there has been some development in this space.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant