Skip to content

Create Index objects even if dates are out of bounds #1

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

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

shoyer
Copy link
Owner

@shoyer shoyer commented Mar 4, 2014

Occasionally, it can be useful to work with datetime objects that cannot be
expressed as np.datetime64 objects with ns precision.

PeriodIndex is currently the only way to make a pandas.Index object consisting
of such datetime objects. But sometimes we really want our index objects to
consist of datetimes, even if they are a less efficient way to represent
dates.

This patch allows for falling back to creating generic Index objects if an
OutOfBoundsDatetime exception is encountered when attempting to create an
Index.

shoyer added 6 commits March 3, 2014 21:21
Occasionally, it can be useful to work with datetime objects that cannot be
expressed as np.datetime64 objects with ns precision.

PeriodIndex is currently the only way to make a pandas.Index object consisting
of such datetime objects. But sometimes we really want our index objects to
consist of datetimes, even if they are a less efficient way to represent
dates.

This patch allows for falling back to creating generic Index objects if an
OutOfBoundsDatetime exception is encountered when attempting to create an
Index.
shoyer pushed a commit that referenced this pull request Sep 10, 2015
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

Successfully merging this pull request may close these issues.

1 participant