I have working code. It's just got 100s of asserts in it right now to catch bugs for now. I'm looking for an elegant solution to this. I've put the files up on pasebin. I'm not proud of them. :) I just needed to get some debugging done quickly and didn't have time for a clean solution at the moment.
Here are the patches http://pastebin.com/1Wr0sCWA __init__.py http://pastebin.com/2cfkTwVb debugger.py http://pastebin.com/29N21fYp settings.py Here is the new file http://pastebin.com/dLALEpZi safe_open.py Shawn On Mon, May 16, 2011 at 10:59 AM, Andreas Kloeckner <[email protected]> wrote: > On Fri, 13 May 2011 18:06:56 -0700, Shawn Lee <[email protected]> wrote: >> 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. > > Ok, I've reverted my attempted fix. Let me know if you come with a > better one. > > Andreas > _______________________________________________ Pudb mailing list [email protected] http://lists.tiker.net/listinfo/pudb
