In this question I asked about a function composition operator in Python. @Philip Tzou offered the following code, which does the job.
import functools
class Composable:
def __init__(self, func):
self.func = func
functools.update_wrapper(self, func)
def __matmul__(self, other):
return lambda *args, **kw: self.func(other.func(*args, **kw))
def __call__(self, *args, **kw):
return self.func(*args, **kw)
I added the following functions.
def __mul__(self, other):
return lambda *args, **kw: self.func(other.func(*args, **kw))
def __gt__(self, other):
return lambda *args, **kw: self.func(other.func(*args, **kw))
With these additions, one can use @
, *
, and >
as operators to compose functions. For, example, one can write print((add1 @ add2)(5), (add1 * add2)(5), (add1 > add2)(5))
and get # 8 8 8
. (PyCharm complains that a boolean isn't callable for (add1 > add2)(5)
. But it still ran.)
All along, though, I wanted to use .
as a function composition operator. So I added
def __getattribute__(self, other):
return lambda *args, **kw: self.func(other.func(*args, **kw))
(Note that this fouls up update_wrapper
, which can be removed for the sake of this question.)
When I run print((add1 . add2)(5))
I get this error at runtime: AttributeError: 'str' object has no attribute 'func'
. It turns out (apparently) that arguments to __getattribute__
are converted to strings before being passed to __getattribute__
.
Is there a way around that conversion? Or am I misdiagnosing the problem, and some other approach will work?
I am actually unwilling to provide this answer. But you should know in certain circumstance you can use a dot "
.
" notation even it is a primary. This solution only works for functions that can be access fromglobals()
:To test:
You can't have what you want. The
.
notation is not a binary operator, it is a primary, with only the value operand (the left-hand side of the.
), and an identifier. Identifiers are strings of characters, not full-blown expressions that produce references to a value.From the Attribute references section:
So when compiling, Python parses
identifier
as a string value, not as an expression (which is what you get for operands to operators). The__getattribute__
hook (and any of the other attribute access hooks) only has to deal with strings. There is no way around this; the dynamic attribute access functiongetattr()
strictly enforces thatname
must be a string:If you want to use syntax to compose two objects, you are limited to binary operators, so expressions that take two operands, and only those that have hooks (the boolean
and
andor
operators do not have hooks because they evaluate lazily,is
andis not
do not have hooks because they operate on object identity, not object values).