Skip to content
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

DOC: Fix warning for PyArray_MapIterNew. #24130

Merged
merged 2 commits into from
Jul 9, 2023
Merged
Changes from all commits
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
4 changes: 2 additions & 2 deletions doc/source/dev/internals.code-explanations.rst
Original file line number Diff line number Diff line change
Expand Up @@ -270,7 +270,7 @@ has three different branches and one special case:
as if there is no subarray but needs some care during setup.

Deciding what case applies, checking broadcasting, and determining the kind
of transposition needed are all done in :c:func:`PyArray_MapIterNew`. After
of transposition needed are all done in ``PyArray_MapIterNew``. After
setting up, there are two cases. If there is no subarray or it only has one
element, no subarray iteration is necessary and an iterator is prepared
which iterates all indexing arrays *as well as* the result or value array.
Expand All @@ -283,7 +283,7 @@ iteration.

When advanced indices are next to each other transposing may be necessary.
All necessary transposing is handled by :c:func:`PyArray_MapIterSwapAxes` and
has to be handled by the caller unless :c:func:`PyArray_MapIterNew` is asked to
has to be handled by the caller unless ``PyArray_MapIterNew`` is asked to
allocate the result.

After preparation, getting and setting are relatively straightforward,
Expand Down
Loading