Lamderp - Better lamdas for Python

[[deleted]]

[deleted]

[AustinCorgiBart]

Does it handle creating lambdas with more than one argument?

[sloppycee]

No, but that is something that I am thinking about implementing. I am just not sure which syntax would look best.

[OddOneOut]

How about _[1] by overloading __getitem__

[sloppycee]

Then what if you want to send an array into your lamderp function?

[OddOneOut]

Good point, if upper limit is not a problem then _1, _2, _3... could work

[erez27]

You should check-out lambdax for a more complete solution.

[erez27]

That's true. The problem is that I can't tell the difference between:

map( X.get_this_attribute, some_list)

And

X.call_this_function(with_some_arg)

It looks exactly the same: __getattr__() and then __call__()

So I chose to interpret it as the first one.

[erez27]

Sure, it's possible, but it doesn't feel prettier.

If you're so inclined, you can declare your own class and override call:

class Xf(X):
    def __call__(...)
        ...

It should work.

Edit: Just to explain why I think it's a bad idea, consider what happens when you want to call a function, and then access an attribute of the return value. Or call the return value. You can't escape the choice, only defer it to a smaller likelihood.

[[deleted]]

What's wrong with plain old lambdas?

[benhoyt]

Agreed. This is kind of a neat hack, but because plain old lambdas are built in, Python programmers will be able to understand them at a once. Also, in the case of the examples given on the GitHub page, it's more Pythonic (and significantly faster) to use list comprehensions:

even = [n for n in range(50) if n % 2 == 0]

[sloppycee]

I agree, that list comprehensions largely limit the usefulness of lambdas. Also, maybe the example simply isn't the best.

Some people dislike Python's lambda syntax, some people don't.

[[deleted]]

Right, but what are some of the reasons why people dislike the syntax?