On Fri, 2007-04-20 at 10:03 +0000, simonbun wrote:
> I've "svn up -r #"d through all the revisions and it seems  4905
> causes it. Wich is the first import of the code.
> 
> Normally more people would have noticed this problem if it's been
> around since 4905, so i'm guessing those changes somehow clash with my
> dev server setup...
> 
> Any clues as to what my cause it? I've tried deactivation psyco
> (grasping at straws here), but no change.

Truly odd. The thing is, traceback.extract_stack() is written in Python
and works exactly as you might expect.

Maybe inside your try/except block, check if you have a
sys.tracebacklimit attribute and, if so, is it zero by any chance? I'm
just wondering if that's something your system is setting. It's not
normally present, but you can set it to control the depth of traceback
information.

Oh .. and one other thought, what does traceback.extract_tb() show
inside the "except" clause after catching the index error? Does it show
a full and useful traceback -- including all the stack frames? I suspect
it will, which will be mystifying, but interesting to know nevertheless.

If I understood what was causing this problem and that we could deem it
truly harmless, I'd be willing to put in a workaround for the specific
case of extract_stack() being empty. However, at the moment, it's too
weird to do that, since I don't understand why it's needed.

Sorry to keep hitting you with questions requiring poking at your dev
server, but this is a real mystery and I feel a bit responsible to try
and fix it (I'd be quite happy if somebody else wanted to feel
responsible and fix it instead, but that's unlikely).

Regards,
Malcolm


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to