[Python-Dev] Making proxy types easier to write and maintain (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Wed Mar 19 21:23:13 CET 2014
- Previous message: [Python-Dev] Making proxy types easier to write and maintain
- Next message: [Python-Dev] Making proxy types easier to write and maintain
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 19 Mar 2014 20:15:15 +0000 Paul Moore <p.f.moore at gmail.com> wrote:
On 19 March 2014 18:46, Antoine Pitrou <solipsis at pitrou.net> wrote: > In http://bugs.python.org/issue19359#msg213530 I proposed to introduce a "proxy > protocol" (proxy / tpproxy) that would be used as a fallback by > PyObjectLookupSpecial to fetch the lookup target, i.e.: > > def PyObjectLookupSpecial(obj, name): > tp = type(obj) > try: > return getattr(tp, name) > except AttributeError: > return getattr(tp.tpproxy(), name) > > What do you think?
Would that increase the size of type objects? Would that matter? (There's a similar question that came up in the thread about adding the @ operator over on python-ideas, which is what made me think of it...)
One additional slot is one additional pointer field, which is mostly trivial in a type object.
Regards
Antoine.
- Previous message: [Python-Dev] Making proxy types easier to write and maintain
- Next message: [Python-Dev] Making proxy types easier to write and maintain
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]