-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
gh-99521: add notation key explaining in built-in functions #142641
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
Closed
+9
−0
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,15 @@ | ||
| .. XXX document all delegations to __special__ methods | ||
| .. _built-in-funcs: | ||
|
|
||
| Notation | ||
| -------- | ||
|
|
||
| In the function signatures that follow you may see some special markers: | ||
|
|
||
| - ``/`` (a single forward slash) — indicates that the parameters before it are *positional-only*. Parameters to the left of ``/`` must be supplied positionally and cannot be passed as keyword arguments. For example, ``repr(object, /)`` means ``object`` is positional-only. | ||
|
|
||
| - ``*`` (a single asterisk) — indicates that the parameters following it are *keyword-only* and must be supplied using their parameter names. | ||
|
|
||
|
Comment on lines
+7
to
+12
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please wrap the text under 80 characters. |
||
| Built-in Functions | ||
| ================== | ||
|
|
||
|
|
||
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Please make sure that the Notation title is not a subtitle compared to "Built-in" functions otherwise it becomes weird. I wonder whether we should put this in functions.rst or intro.rst as well. In addition there were multiple options proposed in the issue and no consensus was reached.