Databases
StackOverflow2013
Postsdbo
POSpyder + PythonXY - Python Interpreter and IPython OUTPUT issues - no output
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSpyder + PythonXY - Python Interpreter and IPython OUTPUT issues - no output
    text
    copied!<p>In Spyder (installed together with PythonXY) on a win 8 64 bit machine, both the Python interpreter and the IPython interpreter have output issues. </p> <p>The first one, gives output at first but as soon as I run some particular code, it doesn't anymore. I noticed the issue happens easily if I get some error messages first, or if I use ipdb, but not only. Even with some code that run smoothly, it happens that it stops giving output afterward.</p> <p>IPython is opened in a dedicated IPython console tab, although it's kernel opens a window in the console tab (this did not happen to me with previous versions of spyder and it all opened in the console tab). I need to input commands to the interpreter in the IPython console tab window, but the output is sent to the console tab window instead. Very annoying.</p> <p>Anybody having the same issues? Solutions?</p> <p>Thanks a lot!</p> <p>Edit for Carlos Cordoba:</p> <p>So, for example, in the normal Python interpreter I do:</p> <pre><code>import module module.method1(par1) </code></pre> <p>where method1 has no errors in it. The method works fine and I get the right output. If I try method2 which contains an error, I get no output.</p> <pre><code>module.method2(par2) </code></pre> <p>After this, I get no output at all for any code I right. I have to restart the kernel.</p> <p>I could not reproduce the same behavior right away on the "IPython console" window. It displays the error message correctly and the output keeps coming out correctly. However, if I use ipdb there, the output goes to the Kernel window instead of the console window, which is inconvenient.</p> <p>Thank you!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload