I ended up just adding a bit to my local version. I added a new signal, 'reload_spyder_breakpoints(filename)' to plugins/editor.py and caught it in externalconsole.py. That then looks at the current tab widget and asks its monitor to run a new function I patched into SpyderPdb in sitecustomize.py. It touches 4 files, but it didn't seem too hideous.
For now, my patched in function is just clearing all breakpoints for the file using Pdb's clear_all_file_breaks( filename ) and then loading the ones from CONF as the existing set_spyder_breakpoints does. If I get ambitious, I might change that to leave the ones that are unchanged in place (matching of file, line & condition string) since right now the numbering of all breakpoints in the file changes when you adjust any one. But it is a start. Doug On Thursday, March 7, 2013 4:55:59 PM UTC-5, Doug Bonar wrote: > > Thanks Jed. Not the answers I wanted to hear, but glad to know I wasn't > missing anything. > > > On Wednesday, March 6, 2013 5:41:37 PM UTC-5, Doug Bonar wrote: >> >> Can I set the graphically? >> >> In spyderlib/plugins/editor.py I see breakpoint related actions being >> set up, but I can't find the breakpoint_menu anywhere as an actual UI >> widget. That said, F12 does put a dot in the edge of the file -- looks >> like it should be a breakpoint. Unfortunately, it I start the debugger, >> then create a breakpoint, the debugger doesn't seem to see it. >> >> So, a 2-part question. >> 1) Is there some way other than F12 to set breakpoints? >> 2) Is there a way to add a breakpoint while the debugger is running? >> >> Thanks >> > -- You received this message because you are subscribed to the Google Groups "spyder" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/spyderlib?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
