Comparing class methods using `is` is wrong?

[Rosuav (Chris Angelico)]

@komoto48g

I wanted to make an adapter function that takes a method and returns a function that can accept at least one GUI event argument; Otherwise, it returns the method as-is if not needed to change. I noticed the problem when I created the test code in which assert a.call is f(a.call) always fails even if f does nothing. Whatever, I don’t think it is a general use case…

That makes sense. Since this is a bit of an unusual case, I would spell it in a slightly longer-winded way and make it clear that you’re testing whether the returned function is the same as the argument:

assert (orig := a.call) is f(orig)

or, of course, breaking it out onto two lines if that is appropriate to what you’re doing.

[komoto48g (Kazuya O'moto)]

Thanks, but it seems yet tricky to me…
I would prefer assert a.call == f(a.call) to walrus.