[issue40846] Misleading line in documentation

2020-06-03 Thread J Arun Mani
J Arun Mani added the comment: Hi. Thanks for your follow-up. I created a PR, since I signed CLA today, the PR has some labels indicating it. :p Thanks -- nosy: -python-dev ___ Python tracker _

[issue40846] Misleading line in documentation

2020-06-03 Thread Roundup Robot
Change by Roundup Robot : -- pull_requests: +19831 pull_request: https://github.com/python/cpython/pull/20603 ___ Python tracker ___ ___

[issue40846] Misleading line in documentation

2020-06-03 Thread Roundup Robot
Change by Roundup Robot : -- keywords: +patch nosy: +python-dev nosy_count: 4.0 -> 5.0 pull_requests: +19830 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20602 ___ Python tracker _

[issue40846] Misleading line in documentation

2020-06-02 Thread Jim Fasarakis-Hilliard
Jim Fasarakis-Hilliard added the comment: A simple substitution of 'types' with 'kind' should do it. This aligns with the terminology [1] used in the glossary. [1] https://docs.python.org/3/glossary.html#term-parameter -- nosy: +Jim Fasarakis-Hilliard ___

[issue40846] Misleading line in documentation

2020-06-02 Thread Rémi Lapeyre
Rémi Lapeyre added the comment: Hi, thanks for pointing this out. I think "type" here is not about the type of the object but whether it is: - positional-only - positional or keyword - variadic positional - keyword-only - variadic keyword The wording could certainly be improved as it is

[issue40846] Misleading line in documentation

2020-06-02 Thread J Arun Mani
New submission from J Arun Mani : Hi. In docs : https://docs.python.org/3/faq/programming.html#faq-argument-vs-parameter it says "Parameters define what types of arguments a function can accept." This is not true. Python's functions do not impose any type checking or raise error when the a