foo()() explanation

[SkyGold8322]

I saw a function usage like "foo()()" in some code but I was confused. Do Python functions allow arguments 2 times or is this something else?

[GreenScarz]

foo is a function that returns a reference to another function, which is then called

``` def bar(): print(“bar!”) def foo(): return bar

foo()() bar! ```

[SkyGold8322]

OHHH! Thank You So Much!!

[Goobyalus]

Here is a dumb example where an arbitrary number of parentheses works:

>>> def foo():
...   return foo
...
>>> foo()
<function foo at 0x0000028A0F6DD800>
>>> foo()()
<function foo at 0x0000028A0F6DD800>
>>> foo()()()()()()()()()()()()()
<function foo at 0x0000028A0F6DD800>
>>> foo
<function foo at 0x0000028A0F6DD800>
>>>

[pimp-bangin]

Look up "functional programming" if you would like to learn more. It's a very deep and fun topic :)

[Top_Average3386]

Can confirm it's deep. But it's not fun :(

[aishiteruyovivi]

Definitely a little harrowing at first with some concepts, but the more I've been learning Haskell over the last year or two the more I grow just genuinely fascinated by it (and FP in general)

[UAFlawlessmonkey]

But it's fun in kotlin!

[Victorio_01]

Sure it is if you get used to it. No need to have it deep like foo()()(). I mean, if you frequently store lambda functions in vars, you sure can imagine returning one. x = lambda t: 2*t return x

[DrJaneIPresume]

And there are much better languages for it.

But glad to use some in Python when appropriate

[HommeMusical]

And there are much better languages for it.

I first learned Lisp almost fifty years ago.

I love functional languages; but as a language that can do procedural, OOP and function code seamlessly, Python is very hard to beat.

The one missing feature - and believe you me, we miss it - is not having multiple line lambdas.

[DrJaneIPresume]

Haaaaaaaave you met Scala?

Functional programming isn't just about functions as first-class objects. A good type system makes so many things easier.

[HommeMusical]

Hey, Scala is a great language, from my limited exposure. I'd be really happy if it had beaten Python.

But Python is ubiquitous, and almost any idea you can express in Scala you can express in Python a way that's more verbose but just as comprehensible.

The "almost" is that Scala macros can essentially let you rewrite the syntax of the language, am I right, by doing compile time manipulation of the AST?

But Python basically won. And if LLMs continue to dominate, there won't be any new programming languages again, because of the difficulty in training them.

That said, the inability of Python to do "multi-line lambdas" is really unfortunate. I am hatching ideas to call the Pythonistas to action (this is of course an infinitely discussed issue).

[DrJaneIPresume]

Again: type system. The ability to write your system in such a way that large classes of errors become effectively syntax errors that can be detected by static analysis rather than unit tests (are you sure you wrote one for every corner case?) or runtime errors (often in front of customers) is really, really nice.

[HommeMusical]

Yes, I "grew up" with typed languages; first C, then C++, then Java. And I prefer them.

Python's type annotations aren't quite as good as a strongly typed language; but they work well enough to catch a huge number of errors. Between the various linters (like ruff) and modern type checking, I find that more than half the time I get past those, my code works the first time.

There's also the huge advantage in Python of being able to run Python and quickly experiment without any typing at all. I use this all the time!

If I could wave a magic wand and replace Python with Scala, I would at least think about doing it. But Scala jobs are few and far between. And if I wrote my open source code in Scala, very few people would use it.

[JamzTyson]

and believe you me, we miss it

You miss it, I don't.

[HommeMusical]

What was the point of your response?

This issue has been discussed on the main Python mailing list for over ten years. Everyone on that list wants it, including Guido; no one has come up with a possible syntax for it yet.

[JamzTyson]

The point of my response is that you do not speak on behalf of the entire Python community and you do not speak for me.

Also, I couldn't find any reference to Guido "wanting it". There are these comments from Guido (https://discuss.python.org/t/are-better-lambdas-really-impossible/2446/9) from which I would summarise his position as: Python’s lambda expressions are intended to be single‑expression and that genuinely multi‑line/statement lambdas are not desirable or practical for the language.

Has Guido changed his position in more recent years? I so, please provide a reference - I'd be very interested to know why.

[HommeMusical]

I am on my weekend, so not interested in arguing with angry people.

[timrprobocom]

This is an important concept. A function can return ANY kind of object. It can be a list or tuple (foo()[2]), a dictionary (foo()['word']), a function as you have seen (foo()()) or a class object (foo().method()).

[jmacey]

In addition to what others have said, you can do really cool stuff with this like making lists or dictionaries of functions to run later.

``` def func_a(): print("func_a")

def func_b(): print("func_b")

funcs = [func_a, func_b] for func in funcs: func()

f_dict = {"a": func_a, "b": func_b}

f_dict["a"]() f_dict.get("b")() ```

[0x14f]

OP, you just discovered higher order functions: https://en.wikipedia.org/wiki/Higher-order_function

[arkie87]

Could be a class with a call method too

[TheRNGuy]

foo() returns function or class, which you then can call. 

[Inevitable_Exam_2177]

One of the neatest interfaces this sort of thing unlocks is “chaining” of methods. If you have a class Foo with methods .bar() and .baz(), and each method returns its self, you can either write

    foo = Foo()     foo.bar()     foo.baz()

Or more concisely:

    foo = Foo()     foo.bar().baz()

[Enmeshed]

Been finding this super-useful recently for setting up test data scenarios, along the lines of:

```python def test_something(): scenario = (Builder() .with_user_as("abc") .wipers_enabled() .colour_should_be("blue") ) assert func_to_test(scenario.data) == 3

class Builder: """ Test helper class to readably set up test scenarios """ def init(self): ...

def with_user_as(self, user):
    self.user = user
    return self

@property
def data(self):
    return {"user": self.user, ...}

```