This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | kundeng06 |
|---|---|
| Recipients | PiDelport, Rhamphoryncus, barry, georg.brandl, gvanrossum, jcea, jkrukoff, kundeng06, ncoghlan, rhettinger, terry.reedy |
| Date | 2008年07月15日.09:26:42 |
| SpamBayes Score | 0.13324325 |
| Marked as misclassified | No |
| Message-id | <1216114005.72.0.890569039714.issue643841@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Hi, I was trying to implement a generic proxy class with some restricting behaviors and then I bumped into this complication. May I ask what the conclusion is going to be in the long run? I guess my question is that 1> is it just going to be a documentation change (first)? 2> is it technically difficult(other things are going to be broken because of this change) or very inefficient to make the behavior of special method lookup same as normal methods? 2> Otherwise, what is the rationale behind keeping the differences? thank you. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月15日 09:26:46 | kundeng06 | set | spambayes_score: 0.133243 -> 0.13324325 recipients: + kundeng06, gvanrossum, barry, georg.brandl, rhettinger, terry.reedy, jcea, ncoghlan, Rhamphoryncus, jkrukoff, PiDelport |
| 2008年07月15日 09:26:46 | kundeng06 | set | spambayes_score: 0.133243 -> 0.133243 messageid: <1216114005.72.0.890569039714.issue643841@psf.upfronthosting.co.za> |
| 2008年07月15日 09:26:44 | kundeng06 | link | issue643841 messages |
| 2008年07月15日 09:26:43 | kundeng06 | create | |