Comment 1 for bug 1073983

Revision history for this message
Andreas Roehler (a-roehler) wrote : Re: [Bug 1073983] [NEW] In "split-windows-on-execute" starts 1 more python to additional ipython shell

Am 01.11.2012 15:53, schrieb Yaroslav Halchenko:
> Public bug reported:
>
> so I have a .py file loaded, and *IPython* visible (py-shell-name
> globally "ipython"). Now if I C-c C-c -- I get 1 more buffer with a
> Python shell, while code correctly executed in *Ipython" (remains
> visible, *Python* buffer is added in additional split)
>
> FWIW: latest lines in Messages
>
> py-shell-switch-buffers-on-execute: t
> Wrote /home/yoh/.tmp/ipython-22782F8D.py
> py-shell-switch-buffers-on-execute: nil
> py-split-windows-on-execute-p: t
> Wrote /home/yoh/.tmp/ipython-22782SGK.py
> Wrote /home/yoh/.tmp/ipython-22782fQQ.py
> Wrote /home/yoh/.tmp/ipython-22782saW.py
> Buffer has a running process; kill it? (y or n) # That is where I forced to kill that additional *Python* buffer
> Wrote /home/yoh/.tmp/ipython-227825kc.py
> byte-code: End of buffer
>
> ** Affects: python-mode
> Importance: Undecided
> Status: New
>

can't reproduce.
Please send some example code which triggers the bug.

thanks,

Andreas