On Sat, Jul 12, 2008 at 3:41 PM, Michael Foord
<[EMAIL PROTECTED]> wrote:
>
> Well - if this is a new style class then '__getitem__' shouldn't be looked
> through __getattr__ anyway.
Yes, there was an issue with the way I defined __getitem__,
__contains__, etc. And of course, if they don't exist t
2008/7/12 Dan Eloff <[EMAIL PROTECTED]>:
> Hopefully this stack trace will be enough to track this down, but if
> it's not please ask for any information you need.
>
> The value of attr is "__getitem__".
Well - if this is a new style class then '__getitem__' shouldn't be looked
through __getattr
> Well that *looks* like a normal Python error. Is self.ns iterable? (It
> either needs to be iterable, have a __getitem__ that supports integer
> indexes or have a __contains__ method).
>
Whoops. You're right, there was something wrong with my __contains__
method. None of that explains the first
Dan Eloff wrote:
This error is exploding all around me. I can get you a dozen more
stack traces from different places in my code. There's some kind of
unpacking happening (at
Microsoft.Scripting.Interpretation.Interpreter.InterpretTryStatement(InterpreterState
state, Expression expr) ?) that is b
This error is exploding all around me. I can get you a dozen more
stack traces from different places in my code. There's some kind of
unpacking happening (at
Microsoft.Scripting.Interpretation.Interpreter.InterpretTryStatement(InterpreterState
state, Expression expr) ?) that is breaking a lot of th
Hopefully this stack trace will be enough to track this down, but if
it's not please ask for any information you need.
The value of attr is "__getitem__".
-Dan
ValueError: too many values to unpack
game\models\__init__.py
Line 12: except KeyError:
Line 13: print attr
Line 14:
