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.

Sign up for GitHub

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

Jump to bottom

Investigate standardizing on Pandas datetime instead of Numpy datetime #187

Open
pscheidler opened this issue Feb 25, 2022 · 0 comments
Open

Investigate standardizing on Pandas datetime instead of Numpy datetime #187

pscheidler opened this issue Feb 25, 2022 · 0 comments
Assignees
@StokesMIDE
Labels
development Related to development issues (package deployment, project organization, etc.) enhancement New feature or request

Comments

@pscheidler
Copy link
Member

pscheidler commented Feb 25, 2022 •
edited by StokesMIDE
Loading

Brought up in meeting on Feb 25:

It is worth considering using the Pandas date time objects consistently, wherever we currently use a numpy.datetime64.

numpy.datetime64 does not include time zone information. The function to_pandas() has been modified to explicitly use a pandas.DatetimeIndex with TZ info (see pr #184); using a np.datetime64 as a Dataframe index implicitly creates one, anyway.

I'm not sure where np.datetime64 is used, but it should be investigated.
@StokesMIDE StokesMIDE added enhancement New feature or request development Related to development issues (package deployment, project organization, etc.) labels Apr 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@StokesMIDE StokesMIDE

Labels
development Related to development issues (package deployment, project organization, etc.) enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@StokesMIDE @pscheidler