GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing mail.python.org — [Python-Dev] Issue 643841: Including a new-style proxy base class in 2.6/3.0 [Python-Dev] Issue 643841: Including a new-style proxy base class in 2.6/3.0Armin Ronacher armin.ronacher at active-4.comMon May 26 22:03:38 CEST 2008
Hi, Nick Coghlan <ncoghlan <at> gmail.com> writes: > One of the tasks where classic classes are currently far superior to > new-style classes is in writing proxy classes like weakref.proxy - cases > where nearly all operations need to be delegated to some other object, > with only a few being handled via the proxy type object itself. Yes. I stumbled upon that multiple times when writing proxies for thread locals. The solution I came up with is rather ugly but works at least: http://dev.pocoo.org/projects/werkzeug/browser/werkzeug/local.py#L202 The main problem with such proxies is that especially builtin types perform various type checks which break proxies sooner or later anyways (currently even abstract base classes implementing a compatible interface). So as soon as you start doing something like some_list + proxy_to_list you get a TypeError. Regards, Armin
More information about the Python-Dev mailing list |
| You are visitor 01402520 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |