# PEP 570: Python Positional-Only Parameters **URL:** \ **Category:** PEPs\ **Created:** [March 28, 2019, 12:04am UTC](https://discuss.python.org/t/pep-570-python-positional-only-parameters/1078 "2019-03-28T00:04:34Z")\ **Posts on this page:** 1\ **Showing post:** 30
**Author:** ![rhettinger](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/rhettinger/32/1129_2.png) [@rhettinger](https://discuss.python.org/u/rhettinger)\ **Post date:** [March 29, 2019, 7:23am UTC](https://discuss.python.org/t/pep-570-python-positional-only-parameters/1078/30 "2019-03-29T07:23:10Z")
> [@pablogsal](#): > > The PEP makes a great effort in describing not only all the situation were positional only arguments are important and solve real problems, Evidence that there isn’t an _important_ problem to be solved: - It doesn’t come up in Python training courses at all - There don’t seem to be any prominent blog posts on the subject - It doesn’t show up in Hacker News comments - There don’t seem to be any recorded talks on the subject - On StackOverflow’s 2,000,000+ Python questions, this comes up almost never - I spend my life answering questions about Python and have never been asked about this - It is rare to see a bug report or tracker issue where this is a root cause. - Most Python programmers don’t even know what the “/” means in help() output – just ask around - If you ask Python consultants what problems they are asked to solve, it won’t be mentioned - Other prominent languages haven’t felt the need to add a “/” notation - Ask full time code reviewers (like Jack D) whether this is a recurring or important issue (the answer is no) The PEP isn’t wrong that there aren’t some issues. It is wrong that there about the significance being enough to warrant a grammar change that will be inflicted on 100% of the users in a way they mostly won’t be able to ignore when reading code. --- _[View the full topic](https://discuss.python.org/t/pep-570-python-positional-only-parameters/1078)._