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 p-ganssle
Recipients barry, brett.cannon, docs@python, gregory.p.smith, ncoghlan, p-ganssle, pablogsal, rhettinger, tim.peters, vstinner, willingc
Date 2019-06-04.02:46:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559616367.27.0.957650702029.issue37134@roundup.psfhosted.org>
In-reply-to
Content
> I respectfully disagree with logic, "the language now permits this, so we should change all the docs to display it everywhere".  That moves it from optional knowledge to mandatory knowledge, from a day ten lesson to a day one lesson, from "once in a while, a user may benefit from being able to mark arguments as positional-only" to the category of "every single user will see this every time they see the docs".  There is a huge difference.

A decent part of the reasoning for the PEP was actually to create a standard way to document when arguments to a function are positional-only. By adopting the notation (already used in the numpy documentation IIRC), it makes a concise documentation clear.

Another part of the PEP's reasoning was that this notation is difficult to understand at least partially because it is rarely encountered, so "people don't understand it" as a reason to exclude it from the documentation becomes a bit of a self-fulfilling prophecy.

I am not really an expert in documentation and front-end design, but maybe it would be possible to have some sort of unobtrusive tooltip that activates on signatures that contain positional-only arguments?
History
Date User Action Args
2019-06-04 02:46:07p-gansslesetrecipients: + p-ganssle, tim.peters, barry, brett.cannon, rhettinger, gregory.p.smith, ncoghlan, vstinner, docs@python, willingc, pablogsal
2019-06-04 02:46:07p-gansslesetmessageid: <1559616367.27.0.957650702029.issue37134@roundup.psfhosted.org>
2019-06-04 02:46:07p-gansslelinkissue37134 messages
2019-06-04 02:46:07p-gansslecreate