[Python-Dev] Making proxy types easier to write and maintain
Paul Moore
p.f.moore at gmail.com
Wed Mar 19 21:15:15 CET 2014
More information about the Python-Dev mailing list
Wed Mar 19 21:15:15 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 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__ / tp_proxy) that would be used as a fallback by > _PyObject_LookupSpecial to fetch the lookup target, i.e.: > > def _PyObject_LookupSpecial(obj, name): > tp = type(obj) > try: > return getattr(tp, name) > except AttributeError: > return getattr(tp.tp_proxy(), 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...) Paul
- 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 ]
More information about the Python-Dev mailing list