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

bpo-30059: Py_Ellipsis in C API documentation #1018

Merged
merged 3 commits into from
Apr 14, 2017
Merged
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
Prev Previous commit
Next Next commit
seperate heading for ellipsis object
  • Loading branch information
MSeifert04 committed Apr 13, 2017
commit 755679f3bbda6feb29a9c777c2fffa8879ef0db1
12 changes: 8 additions & 4 deletions Doc/c-api/slice.rst
Original file line number Diff line number Diff line change
@@ -1,9 +1,7 @@
.. highlightlang:: c

.. _slice-objects:

Slice Objects
-------------
Ellipsis Object
Copy link
Member

Choose a reason for hiding this comment

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

Since the file is called slice.rst and slices are more used than Ellipsis I think Slice Objects should be before Ellipsis Object.

---------------


.. c:var:: PyObject *Py_Ellipsis
Expand All @@ -13,6 +11,12 @@ Slice Objects
:c:data:`Py_None` it is a singleton object.


.. _slice-objects:

Slice Objects
-------------


.. c:var:: PyTypeObject PySlice_Type

The type object for slice objects. This is the same as :class:`slice` in the
Expand Down