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 | ncoghlan |
|---|---|
| Recipients | PiDelport, Rhamphoryncus, barry, georg.brandl, gvanrossum, jcea, jkrukoff, kundeng06, ncoghlan, rhettinger, terry.reedy |
| Date | 2008年07月15日.09:52:15 |
| SpamBayes Score | 0.00013895321 |
| Marked as misclassified | No |
| Message-id | <1216115537.93.0.453145448789.issue643841@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
There are both speed and correctness reasons for special methods being looked up the way they are, so the behaviour isn't going to change. Aside from providing additional details in the language reference on how special methods are looked up (and the reasons things are done that way), the only change that might eventually happen in this area is the inclusion of a mixin class in the standard library to assist in writing classes which delegate most operations to another object. That part won't happen before 2.7/3.1 though (if it happens at all). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月15日 09:52:18 | ncoghlan | set | spambayes_score: 0.000138953 -> 0.00013895321 recipients: + ncoghlan, gvanrossum, barry, georg.brandl, rhettinger, terry.reedy, jcea, Rhamphoryncus, jkrukoff, PiDelport, kundeng06 |
| 2008年07月15日 09:52:18 | ncoghlan | set | spambayes_score: 0.000138953 -> 0.000138953 messageid: <1216115537.93.0.453145448789.issue643841@psf.upfronthosting.co.za> |
| 2008年07月15日 09:52:17 | ncoghlan | link | issue643841 messages |
| 2008年07月15日 09:52:15 | ncoghlan | create | |