Debugger not responding after copying text from IPython Console

[spyder-bot]

From [email protected] on 2014-04-09T17:41:56Z

Please note that reporting bugs from Spyder's help menu ("?" > "Report
issue...") will fill version details for Spyder, Python and Qt in this description for you.

What steps will reproduce the problem?

1. Start debugging (Ctrl+F5) inside an IPython console
   1. Select any text in the IPython Console
   2. Copy (Ctrl+C) What is the expected output? What do you see instead? Text should be copied to clipboard.
      Instead, the clipboard is unchanged, and the debugger no longer responds to the Enter key, or to commands from the GUI, though typing into its prompt is still possible. What version of the product are you using? On what operating system? Spyder 2.2.5 on Windows XP

Please provide any additional information below

. The problem does not occur on in the "regular" Python console.

Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1787

[spyder-bot]

From ccordoba12 on 2014-04-16T09:25:01Z

Instead of Ctrl+C you should select your text, do right-click with your mouse and select the option called "Copy".

Does that help?

Labels: Cat-Debugger

[spyder-bot]

From [email protected] on 2014-04-21T14:49:29Z

Copying from the right-click menu works.

[spyder-bot]

From [email protected] on 2014-09-02T08:24:56Z

This bug is still present in the current Spyder 2.3.0 with Python 3.3 under Windows.

Using the mouse as suggested by @-ccordoba12 does work. But for an efficient debugging workflow, it is a major issue being unable to use the extremely useful Ctrl+C keyboard shortcut.

This Spyder bug is especially critical given that (i) the command history is not available while debugging in the IPython console (unlike in the regular console) and (ii) the regular Python console does not work with Python 3 under Windows ( issue #1831 ).

This implies that one has to use Ctrl+C very often while debugging in IPython to copy and modify some of the previous lines.

The bottom line is that unfortunately Spyder is not an efficient option with Python 3 under Windows until the console is fixed.

[spyder-bot]

From ccordoba12 on 2014-09-02T10:06:32Z

The problem with debugging in the IPython console is somehow out of our reach, because we just embed the qtconsole provided by the IPython guys.

I'll try to see if I can fix it and submit a pull request upstream, but I can't promise anything in short time. However, you have to be aware that you can't run arbitrary Python code under the debugger, so that's another limitation.

Unfortunately, I have to say our debugging support leaves a lot to be desired. I have several plans to improve it but all seems to point out that they'll have to wait at least a year to be implemented. Sorry.

[spyder-bot]

From [email protected] on 2014-09-02T10:43:45Z

Thanks @-ccordoba12. I do realize fixing the IPython console is out of your control.

In fact my hope is still that at some point Pierre will manage to bring back the standard Python console to Python 3 Windows users of Spyder. It seems all my issues would be solved in that case.

In the meantime I use IEP when debugging and go back to Spyder for editing...

[spyder-bot]

From ccordoba12 on 2015-01-01T15:19:40Z

Labels: MS-v2.4

[spyder-bot]

From [email protected] on 2015-01-22T00:04:11Z

I can only concur. This is a major limitation in heavy-duty debugging work. Let us hope a solution can be found soon.

[bcolsen]

@ccordoba12 The ipdb debugger says this now when you press 'ctrl-c':

ipdb> --KeyboardInterrupt--
For copying text while debugging, use Ctrl+Shift+C

This may close this issue, unless ctrl-c is required

[ccordoba12]

Yep, that's right. I added that message so that people are not accidentally exited from ipdb while they try to copy some text.

This was fixed in PR #4202.