Re: [Python-Dev] super_getattro() Behaviour

2005-04-14 Thread Phil Thompson
4. Am I missing a more correct/obvious technique? (There is no need to support classic classes.) >>> >>> Hum, I can't think of one, I'm afraid. >>> >>> There has been some vague talk of having a tp_lookup slot in >>> typeobjects, so >>> >>> PyDict_GetItem(t->tp_dict, x); >>> >>> would bec

Re: [Python-Dev] super_getattro() Behaviour

2005-04-14 Thread Michael Hudson
"Phil Thompson" <[EMAIL PROTECTED]> writes: >>> Questions... >>> >>> 1. What is the reason why it doesn't go via tp_getattro? >> >> Because it wouldn't work if it did? I'm not sure what you're >> suggesting here. > > I'm asking for an explanation for the current implementation. Why wouldn't > it

Re: [Python-Dev] super_getattro() Behaviour

2005-04-14 Thread Phil Thompson
> "Phil Thompson" <[EMAIL PROTECTED]> writes: > >> In PyQt, wrapped types implement lazy access to the type dictionary >> through tp_getattro. If the normal attribute lookup fails, then private >> tables are searched and the attribute (if found) is created on the fly >> and >> returned. It is also

Re: [Python-Dev] super_getattro() Behaviour

2005-04-13 Thread Michael Hudson
"Phil Thompson" <[EMAIL PROTECTED]> writes: > In PyQt, wrapped types implement lazy access to the type dictionary > through tp_getattro. If the normal attribute lookup fails, then private > tables are searched and the attribute (if found) is created on the fly and > returned. It is also put into t

[Python-Dev] super_getattro() Behaviour

2005-04-13 Thread Phil Thompson
In PyQt, wrapped types implement lazy access to the type dictionary through tp_getattro. If the normal attribute lookup fails, then private tables are searched and the attribute (if found) is created on the fly and returned. It is also put into the type dictionary so that it is found next time thro