Comment 2 for bug 944401

Am 01.03.2012 23:33, schrieb Richard Stanton:
> Public bug reported:
>
> I'm using the latest trunk version of python-mode (March 1, 2012) under
> OS X, with ipython as my shell. If I open a python script and press C-c
> C-c, a new ipython buffer is created and the script runs fine, though
> the ipython buffer replaces the original script buffer, rather than the
> window splitting into two, which means I now need to manually switch
> buffers to get back to the script file. I think this counts as
> inconvenient behavior, if not an actual bug...
>
> The more serious problem is as follows. After running the program as
> above,
>
> 1) Ask Emacs to kill the *IPython* buffer and agree to kill the running
> python process.
>
> 2) Return to the original script file buffer and press C-c C-c again
>
> A new ipython buffer is created OK, but the script file doesn't run.

if you repeat the command, it should.

First time, if no shell is running, it fails: That bug exists for long,
also mentioned in python.el.

Tried to cure that already, however not successful so far.
That's why python-mode opens a shell already from start - see
`py-start-run-py-shell'

will take another look into though...