-
-
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
Conversation
| 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. | ||
|
|
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 wrap the text under 80 characters.
| Notation | ||
| -------- |
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.
|
Actually, there wasn't a consensus on the issue on what to do (no core dev expressed their opinions as of now) so I'm closing this for now. Sorry but please do not create PR if there isn't a consensus or a maintainer's decision. |
📚 Documentation preview 📚: https://cpython-previews--142641.org.readthedocs.build/