-
-
Notifications
You must be signed in to change notification settings - Fork 31.2k
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
Conversation
@MSeifert04, thanks for your PR! By analyzing the history of the files in this pull request, we identified @birkenfeld, @ashemedai and @loewis to be potential reviewers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to have it documented.
Maybe add details from something like http://stackoverflow.com/a/773472/276047 to explain just what it is for?
@ashemedai Thank you for the feedback. But I don't think the C API would be the best place to explain what it is for. Shouldn't that rather be explained and documented in constants.Ellipsis? |
@MSeifert04 Good point. It's been a while since I looked through the entirety of the documentation. You might be right there, yes. |
Doc/c-api/slice.rst
Outdated
@@ -1,5 +1,16 @@ | |||
.. highlightlang:: c | |||
|
|||
Ellipsis Object |
There was a problem hiding this comment.
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.
As far as I have seen there is no mention of it anywhere. And it's defined along with
sliceobject
so I included it in the documentation there. FWIW: most of the added documentation is copied fromPy_None
.