Hi Somchai, all, Somchai Smythe <[email protected]> writes: > I already emailed you the crash in this thread trying to load python2 > breakpoints on print statements in python3 compiled pudb (which loads > breakpoints for everything even if I'm not working on that file) > causes pudb itself to crash. That was why I made the patch. I don't > think some theme color scheme matters if the debugger is going to > crash; I need the debugger to work. Anything that can cause a syntax > error kills the debugger when loading those breakpoints, because there > is no distinction between python2 and python3 breakpoints. Incorrect > colors (as long as it isn't black text on a black background or > something) still let me get the work done; crashes don't. When a > hello world program kills the debugger, it's a sign there's a problem > with the debugger.
Thanks for taking the time to explain. While I agree that making saved breakpoints 100% bullet-proof would require a bit more work, I believe that what I've just committed to pudb's repository at least addresses your specific issue: Saved breakpoints are now specific to each Python version, saved in a file "breakpoints-2.7" or the like. It also addresses Aaron's complaint by sharing the rest of the configuration across Python 2 and 3. I hope that's an acceptable compromise. Somchai: I apologize that you felt unwelcome and misunderstood in trying to get your issue across. I for one was a bit slow in understanding what you meant--I'm sorry about that. I'll let this change sit for a couple of days (it'd be great if you could give it a whirl) and then release a new version. Andreas
pgpoVDGAGd4Ng.pgp
Description: PGP signature
_______________________________________________ Pudb mailing list [email protected] http://lists.tiker.net/listinfo/pudb
