Create Index objects even if dates are out of bounds #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.