This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients benjamin.peterson, berker.peksag, docs@python, emily.zhao, josh.r, jwilk, larry, lys.nikolaou, ncoghlan, noah.haasis, pradyunsg, rhettinger, veky, zach.ware
Date 2019-03-10.11:46:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I went ahead and merged Lysandros's new FAQ entry (Thank you Lysandros!), as having some level of documentation for this notation is markedly better than the previous "none at all", and the PR added cross-references from the builtins and inspect module docs in addition to adding the FAQ itself.

However, I'm not closing the issue yet as:

- the exact wording could likely stand to be tweaked a bit (in particular, I'm not sure it's a good idea to reference PEP 570 from the FAQ entry)

- we may want to enhance pydoc itself to explain the notation inline (e.g. by appending a footer saying "Note: parameters to the left of ``/`` entries are positional only and cannot be passed by name" after the docstring being displayed when positional only parameters are found, and "Note: parameters to the right of ``*`` and ``*name`` entries are keyword only and can only be passed by name" when keyword only parameters are found)

- we may want to file a follow-up issue proposing that `pydoc` go back to either not marking positional-only parameters at all, or marking them differently (e.g. with "Note: *x*, *y*, and *z* are positional only parameters that cannot be passed by name" after the individual callable docstrings)
Date User Action Args
2019-03-10 11:46:02ncoghlansetrecipients: + ncoghlan, rhettinger, larry, benjamin.peterson, jwilk, docs@python, berker.peksag, zach.ware, pradyunsg, josh.r, veky, emily.zhao, lys.nikolaou, noah.haasis
2019-03-10 11:46:02ncoghlansetmessageid: <>
2019-03-10 11:46:02ncoghlanlinkissue21314 messages
2019-03-10 11:46:02ncoghlancreate