Hello,

I realize this is similar to a couple other recent threads, but I did
not find what I was looking for in them.

I refer to the session, cache, and other pylons globals from time to
time in many controllers. When testing, I have sometimes enabled the
nose pdb flag to debug a test that's failing for an unknown reason.
Unfortunately, I cannot access the session, the cache, g, or h from
the debugger simply because "No object (name: Session) has been
registered for this thread". I'm resorting to print statements to
verify the global state while debugging.

Why I can't access the session doesn't really make sense to me. Why
shouldn't the testing framework be registered? Ignoring that for a
minute, how do I go about registering my debugger thread to access the
global? I have to admit that despite my digging through the source, I
do not have a good understanding of the StackedObjectProxy class and
am constantly doing battle with it.

Justin

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" 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/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to