Skip to content
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions doc/source/indexing.rst
Original file line number Diff line number Diff line change
Expand Up @@ -84,14 +84,17 @@ of multi-axis indexing.

See more at :ref:`Selection by Label <indexing.label>`

- ``.iloc`` is strictly integer position based (from ``0`` to ``length-1`` of
the axis), will raise ``IndexError`` if an indexer is requested and it
is out-of-bounds, except *slice* indexers which allow out-of-bounds indexing.
(this conforms with python/numpy *slice* semantics). Allowed inputs are:
- ``.iloc`` is primarily integer position based (from ``0`` to
``length-1`` of the axis), but may also be used with a boolean
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

their is another section at the very top of indexing.rst where .iloc/.loc are described similarly. pls add there as necessary as well.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it the Different Choices and the Selection By Position sections

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, I hope this is what you were referring to. Tried to make minimal changes as necessary.

array. ``.iloc`` will raise ``IndexError`` if a requested
indexer is out-of-bounds, except *slice* indexers which allow
out-of-bounds indexing. (this conforms with python/numpy *slice*
semantics). Allowed inputs are:

- An integer e.g. ``5``
- A list or array of integers ``[4, 3, 0]``
- A slice object with ints ``1:7``
- A boolean array

See more at :ref:`Selection by Position <indexing.integer>`

Expand Down