FEAT/FIX support methods other than nearest for RangeIndex + end inclusiveness #11113
+76
−13
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.
method=Nonefor RangeIndex slices, and for TransformIndex single point selection.For the latter I had to play some small tricks using
epsto account for floating point error. I think this is the least invasive way to account for the case mentioned in the comments(0.7 - 0.1) / 0.1 = 5.999999999999999instead of6.0Examples:
also passes @dcherian request in #10533 (comment) of equivalency to PandasIndex slicing
whats-new.rstapi.rst