Message56913
I'm trying to keep this as simple as possible, because it seems we're
tending to over-complicate.
We're discussing two distinct issues:
1) Should Delegator delegate calls to callables
2) Should Percolator inherit from Delegator
Have I missed something?
Regarding the first issue, I do think Delegator should do this, because
I view calling a callable as a special case of calling a method. To
illustrate my point, please take the code in example1.py, run it once
with Delegator as it is, and run it again after adding the __call__
method to Delegator's definition.
Regarding the second issue, I don't think I can put my thoughts better
than I already have:
<quote>
As for Percolator, it really "is a" delegator -- it delegates attribute
access to the bottom of the chain, unless it is explicitly overridden.
True, in a "normal" Delegator this overriding can only be done in one
place, and in a Percolator it can also happen in any of the chain's
links. But the concept is identical -- it is a transparent proxy for an
underlying object.
</quote> |
| File name |
Uploaded |
|
example1.py
|
taleinat,
2007-10-29.17:33:50
|
|
| Date |
User |
Action |
Args |
| 2007-10-29 17:33:51 | taleinat | set | spambayes_score: 0.03688 -> 0.03688 recipients:
+ taleinat, kbk |
| 2007-10-29 17:33:51 | taleinat | set | spambayes_score: 0.03688 -> 0.03688 messageid: <1193679231.69.0.826069638441.issue1252@psf.upfronthosting.co.za> |
| 2007-10-29 17:33:51 | taleinat | link | issue1252 messages |
| 2007-10-29 17:33:50 | taleinat | create | |
|