DOC: clarify loc slice step behavior with example closes #63311#63346
+30 −0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
When using .loc[start:stop:step], start/stop use label semantics but step is positional within that range. Added example showing difference from explicit label selection. Closespandas-dev#63311
doc/source/user_guide/indexing.rst Outdated
| .. ipython:: python | ||
| s = pd.Series(range(10), index=[0, 5, 10, 15, 20, 25, 30, 35, 40, 45]) | ||
| s.loc[10:50:5] # (10), then skip 3 positions → 35 only |
Member
There was a problem hiding this comment.
Could you also show a similar example where the index is not numeric?
rhshadrach requested changes Dec 12, 2025
doc/source/user_guide/indexing.rst Outdated
| For more information about duplicate labels, see | ||
| :ref:`Duplicate Labels <duplicates>`. | ||
| Also, when using a slice with a step, such as ``.loc[start:stop:step]``, note that |
Member
There was a problem hiding this comment.
The previous paragraph also starts with Also,, just from a prose standpoint I think we should avoid this.
Suggested change
| Also, when using a slice with a step, such as ``.loc[start:stop:step]``, note that | |
| When using a slice with a step, such as ``.loc[start:stop:step]``, note that |
doc/source/user_guide/indexing.rst Outdated
Comment on lines 436 to 438
| the **positional index** within that label range. This means a stepped slice | ||
| may return different labels than selecting an explicit list, even when they | ||
| appear similar. |
Member
There was a problem hiding this comment.
I think this could be made a little more specific.
Suggested change
| the **positional index** within that label range. This means a stepped slice | |
| may return different labels than selecting an explicit list, even when they | |
| appear similar. | |
| the **positional index** within that label range. This means a stepped slice | |
| will behave differently than using the labels `range(start, stop, step)` when | |
| the index is not contiguous integers. |
Author
Updated per feedback:
The string index example clarifies that step is positional regardless of whether you use integers, characters, or other index types. Pre-commit checks passed ✓ Happy to help, if any further updates are needed :) |
rhshadrach added the Indexing Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
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.
When using .loc[start:stop:step], start/stop use label semantics but step is positional within that range. Added example showing difference from explicit label selection.
Closes#63311
stepwith slice for label-based indexing #63311doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.AGENTS.md.