On Sat, Jan 19, 2013 at 11:33 AM, Uwe Fechner <[email protected]>wrote:
> Hello, > > I am testing the version 2.2.0 beta. > > I love the new debug toolbar, but I want to suggest two > improvements: > > 1. Debugging with ipython and the debug toolbar does not work. > OK, no problem, but than I would expect that the "Debug in > external console" button on the debug toolbar opens a new > Python interpreter before launching the script. > Now you have to do that manually, which is easy to forget > and hard to teach. > > Hi, Ewe. Yes, it is true that the debugging toolbar does not work with IPython consoles right now. That is a limitation that will exist for a while longer until we can figure out the right way to implement it so that it does not require too much tinkering with IPython internals. Actually, the "Debug in external console" button respects the run configuration setting for each particular script (launch the run configuration using F6). If a given script is set to run in the existing console then the debugging will occur in that existing console. If the script is set to run in a new dedicated interpreter then the debugging will be launched in a new interpreter every time. > 2. When the debugging is finished the last line, where the > debugger stopped is still highlighted. That is confusing. > When the debugger is not longer active the highlighting > should be disabled. > > It is Spyder's default behavior to highlight the currently active line in the editor regardless of whether the script is under debug or not, so it doesn't seem to make sense to disable highlighting at the end of debugging. Thanks for the feedback, Jed -- You received this message because you are subscribed to the Google Groups "spyder" 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/spyderlib?hl=en.
