Thanks for the file. Unfortunately, that reverted it back to blank files again. There has to be an open somewhere hidden in an imported routine. A quick override of the open command to log the call + a stack trace should point it out.
I am writing a library that will insure the pudb has a clean set of functions and is not accidentally using overriding core function calls that are setup for unit testing. I'll see if I can figure it out. Shawn On Fri, May 13, 2011 at 4:47 PM, Andreas Kloeckner <[email protected]> wrote: > Hi Shawn, > > On Fri, 13 May 2011 11:54:48 -0700, Shawn Lee <[email protected]> wrote: >> I was having a problem with pudb showing me blank screens in some >> standard library code. The problem occurred when I needed to override >> the __builtins_.open function. I needed to control the open command >> for some unit tests. >> >> So I would be stepping through my code then I would come to a standard >> library call that normally always worked in pudb. Only now it stepped >> into the library and there was no code shown. I found out that the >> issue was caused by the settings.py pudb library calling open and >> using my overridden function. >> >> The solution I came up with was to create a copy of the original open >> function at the top of settings.py and reset open to the original in a >> function and then revert back to the previous overridden setup before >> return from the function. >> >> Remember to backup the original settings.py before you patch. > > I think I've put an equivalent of your patch into git that gets by > without having to patch the builtins module. Can you try that it still > does what you want? > > Thanks, > Andreas > _______________________________________________ Pudb mailing list [email protected] http://lists.tiker.net/listinfo/pudb
