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 mdk
Recipients barry, brett.cannon, bskinn, docs@python, grantjenks, gregory.p.smith, mdk, ncoghlan, p-ganssle, pablogsal, rhettinger, tim.peters, vstinner, willingc
Date 2019-06-04.22:48:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559688505.22.0.668817709249.issue37134@roundup.psfhosted.org>
In-reply-to
Content
FWIW here's my feedback (as a Python teacher and doc guy):

I find that newcomers are good to ignore what they don't understand, so a newcomer exposed to "foo(a, b, /)" will no run away nor cry, he will just ignore the slash and understand that "foo takes two parameters, a and b" and be happy with it.

Then I think that for more advanced people it's nice to have it:

- It's a way to discover it's a valid syntax
- It's a usefull information to use
- It does not take a lot of space
- It's the truth (I mean, displaying "foo(a, b)" for "foo(a, b, /)" is a kind of a lie, I don't like it)

So I'm +1 for using PEP570 syntax in the documentation.
History
Date User Action Args
2019-06-04 22:48:25mdksetrecipients: + mdk, tim.peters, barry, brett.cannon, rhettinger, gregory.p.smith, ncoghlan, vstinner, docs@python, willingc, bskinn, p-ganssle, pablogsal, grantjenks
2019-06-04 22:48:25mdksetmessageid: <1559688505.22.0.668817709249.issue37134@roundup.psfhosted.org>
2019-06-04 22:48:25mdklinkissue37134 messages
2019-06-04 22:48:25mdkcreate