Re:PEP 492 – Coroutines with async and await syntax
by ant6n on Saturday April 18, 2015 @07:35AM
(#9399081)
is there any PEP that makes parens around function call params optional? Tried to find it, no luck.
[ Parent
| on HN ]
Re:PEP 492 – Coroutines with async and await syntax
by actsasbuffoon on Saturday April 18, 2015 @10:19AM
(#9399519)
That would be tricky. Ruby has optional parens for function calls, but it makes it tricky to get a reference to a method without calling it. We have to write "foo.method(:some_method_name)", while the Python equivalent is simply "foo.some_method_name".
You might be able to require parens for methods with no arguments, but optional parens with arguments. It might require some clever hacks in the parser, but I suspect it's possible. The bigger question is whether or not the result would be Pythonic.
Re:PEP 492 – Coroutines with async and await syntax
by ant6n on Saturday April 18, 2015 @07:15PM
(#9401456)
Maybe they could just re-introduce print x as syntactic sugar for galling a print function. Like in Matlab, where the operators (+, *, ..) are just syntactic sugar for calling functions add, mul, ..
Re:PEP 492 – Coroutines with async and await syntax
by DrJosiah on Monday April 20, 2015 @07:16PM
(#9411412)
The Python 3.x print function and 2.x print statement automatically called the __str__ method on an object to get a representation to print to screen. The result is then sent to the appropriate file handle for actual printing (which can be overridden).
Re:PEP 492 – Coroutines with async and await syntax
by tripzilch on Sunday April 19, 2015 @09:28AM
(#9403045)
IPython has this as a configuration option. I only use it in the interactive interpreter (not sure if it works in scripts, but I don't think that's a good idea anyhow). I like being able to type
len flurp
to quickly get the length of an array.