3 ms·
Don't worry, its not coming back. Just goes to prove the old rule - no one reads beyond the headline :) ---- > Why is this being proposed? > > I think we woul
by zaptheimpaler 6y ago
Don't worry, its not coming back. Just goes to prove the old rule - no one reads beyond the headline :)
----
> Why is this being proposed?
>
> I think we would need a very strong reason to consider this,
> and so far I haven't seen any justification other than "because
> we can".
>
(Guidos response below):
There was definitely something of that... I was looking at the new PEG
parser and realized that if people wanted it this would be easy to do. So
I spent a pleasant hour or two coding it up to my satisfaction.
But I was also trying to satisfy some demand. When Python 3 was young,
print becoming a function was one of the most frequent complaints, and
it's still occasionally seen on Twitter. I found at least two StackOverflow
issues about it, but the combined upvote count was less than 100.
An early post in this thread reminded me that IPython has a feature called
"autocall" that allows exactly this syntax. I don't know how popular it is.
However, apparently there the form `f x+1` ends up calling `f("x+1")` (i.e.
stringifying the argument), so introducing similar syntax in Python with
different semantics would hardly be helpful. (If someone wants to start a
debate on argument quoting, please start a new thread, so we can lay this
one to rest.)
All in all, it's clear that there's no future for this idea, and I will
happily withdraw it.
----
- nurettin 6y agoI remember him being present in the github issue tracker before they moved to bugs.python.org. His presence was next to useless when people were reporting problems about the async library. What went on was like; he made comments on his suspicions, someone who actually knows what's going on made a pull request without even commenting on his ramblings. Again and again for years. Now he's looking for validation hacking the parser.