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 | Rhamphoryncus |
|---|---|
| Recipients | PiDelport, Rhamphoryncus, barry, georg.brandl, jcea, jkrukoff, ncoghlan, terry.reedy |
| Date | 2008年05月23日.17:51:11 |
| SpamBayes Score | 0.0 |
| Marked as misclassified | No |
| Message-id | <1211565073.71.0.486751665021.issue643841@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Surely remote proxies fall under what would be expected for a "proxy mixin"? If it's in the stdlib it should be a canonical implementation, NOT a reference implementation. At the moment I can think up 3 use cases: * weakref proxies * lazy load proxy * distributed object The first two could be done if _deref were made overridable. The third needs to turn everything into a message, which would could either do directly, or we could do by turning everything into normal method lookups which then get handled through __getattribute__. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2009年03月09日 14:32:20 | georg.brandl | set | spambayes_score: 0.679952 -> 0.0 |
| 2008年05月23日 17:51:14 | Rhamphoryncus | set | spambayes_score: 0.679952 -> 0.679952 recipients: + Rhamphoryncus, barry, georg.brandl, terry.reedy, jcea, ncoghlan, jkrukoff, PiDelport |
| 2008年05月23日 17:51:13 | Rhamphoryncus | set | spambayes_score: 0.679952 -> 0.679952 messageid: <1211565073.71.0.486751665021.issue643841@psf.upfronthosting.co.za> |
| 2008年05月23日 17:51:12 | Rhamphoryncus | link | issue643841 messages |
| 2008年05月23日 17:51:11 | Rhamphoryncus | create | |