Are there other exceptions being thrown, potentially somewhere on the stack below game\models\__init__.py on line 144? Maybe we're calling a built-in function somewhere that's calling back into your code and is doing something funky with the exception tracking. Can you run this under VS and get the stack traces where all the exceptions are being thrown leading up to the problem?
-----Original Message----- From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dan Eloff Sent: Thursday, January 01, 2009 11:19 AM To: Discussion of IronPython Subject: [IronPython] Odd tracebacks I've been experiencing off tracebacks for several weeks now, mostly I just ignore them because it could be my fault, and it's not a blocker. On AttributeErrors I see very strange tracebacks, impossible tracebacks, sometimes even misleading tracebacks. Have a look at this (complete) traceback: --------------- Phony Traceback Part --------------- at __getattr__ in game\models\__init__.py, line 144 at pairwise in game/utils\functions.py, line 42 at __getattr__ in game\models\__init__.py, line 144 at pairwise in game/utils\functions.py, line 42 at __getattr__ in game\models\__init__.py, line 144 at pairwise in game/utils\functions.py, line 42 at pairwise in game/utils\functions.py, line 42 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 at __getattr__ in game\models\__init__.py, line 144 --------------- Real Traceback Part ----------------- at __getattr__ in beskar\namespace.py, line 46 at __getattr__ in beskar\context.py, line 46 at FleetStrengthDisplay in <string>, line 4 at Content in <string>, line 39 at body in <string>, line 21 at render in beskar\template.py, line 92 at _wrapper in beskar\template.py, line 97 at load_xaml in game\templates\__init__.py, line 18 line 46 of __getattr__ of beskar\namespace.py is where the AttributeError originates, everything beyond that in the traceback is completely out to lunch. Unfortunately this is such odd behavior, I haven't discovered how to reproduce it. Any idea what could cause this? Thanks, -Dan _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com