On Sat, Jan 19, 2013 at 3:21 PM, Uwe Fechner <[email protected]>wrote:
> Dear Jed, > > you write: > "Actually, the "Debug in external console" button respects the run > configuration setting for each particular script" > If that is true than the quickhelp text, that is shown if you hoover over > the red debug button is wrong, because > it ALWAYS says "Debug in external console". > Ah, okay, now I understand the confusion. I will try to clarify the quickhelp. As a more general comment, maybe the challenge is the way the word "external" is used here. In Spyder terminolgy, the internal console means the interpreter in which Spyder itself is running. All other Python consoles are launched in separate processes, and the notion of "external" simply means "a console running in a separate process from Spyder itself". Those external consoles actually come in three flavors under run configuration: the "currently active" interpreter, a separate new "dedicated" interpreter to be used for that script alone, and finally a completely independent python interpreter running in a system terminal to model exactly what would happen if your script was run outside of Spyder. All three of these external console types has an important use case, but I admit that this can seem daunting to understand. > The main problem is that the external or internal console can be either > ipython or python. And I suggest to ALWAYS launch a python (and not > ipython) console if you click the debug button, unless the current console > is already > a python console. > Just to make sure that - if you use the debugging toolbar - that it always > works as expected. > It's actually possible (and completely valid) to launch the debugger into an IPython console using the toolbar. It's just that the stepping commands from the rest of the toolbar won't work yet :). But the typical command line debugging commands that you enter on the prompt do work fine still. I think the answer here is to invest the time to get the debugging toolbar to work right with IPython. Easier said than done, but probably worth it in the end. > With respect to the other little problem: > If it is not possible to " currently active line in the editor" that line > one should be set active after the debugging > has finished to make it clear that the debugger is not longer active. > I'm not quite sure I completely understand this last comment. Could you elaborate? Thanks, again, for the detailed feedback. Jed > > > Am 19.01.2013 21:20, schrieb Jed Ludlow: > > 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. > > > -- > 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. > -- 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.
