>...it's this last one that causes the problem. In the real code, the
>call to type.__setattr__ referred to above seems to lead to a call to
>something like cls.__base__.__dict__[attr].__set__(cls, value).
Uhm ... sounds right, but I a bit confused. Could you please give us a
doctest showing us wh
I have a peculiar problem that, naturally, I cannot reproduce outside
the fairly long-winded code that spawned it. Thus the code snippets here
should be taken as shorthand for what I think are the relevant bits,
without actually leading to the erroneous (or at least undesired)
behaviour described.
