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 | georg.brandl, jkrukoff, ncoghlan, terry.reedy |
| Date | 2008年03月29日.03:47:28 |
| SpamBayes Score | 0.0062691467 |
| Marked as misclassified | No |
| Message-id | <1206762449.43.0.276286197954.issue643841@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The 2.6 and 3.0 documentation has already been updated appropriately. The forward compatible way to handle this is to inherit from object and override the special methods explicitly in the 2.x version (Yes this can make writing proxy objects more tedious, but from our experience with the tempfile module, I would say that the bulk of proxy objects that aren't overriding special methods on a case-by-case basis are probably broken anyway). It may be appropriate to add a -3 warning that is triggered whenever a special method is retrieved via __getattr__ on a classic class. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月29日 03:47:29 | ncoghlan | set | spambayes_score: 0.00626915 -> 0.0062691467 recipients: + ncoghlan, georg.brandl, terry.reedy, jkrukoff |
| 2008年03月29日 03:47:29 | ncoghlan | set | spambayes_score: 0.00626915 -> 0.00626915 messageid: <1206762449.43.0.276286197954.issue643841@psf.upfronthosting.co.za> |
| 2008年03月29日 03:47:28 | ncoghlan | link | issue643841 messages |
| 2008年03月29日 03:47:28 | ncoghlan | create | |