Output from v6 of python-mode different from v5
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-mode.el |
Fix Released
|
Medium
|
Andreas Roehler |
Bug Description
In python-mode v5, when I executed py-execute-buffer on a python script I would get a split window, viewing a buffer called *Python Output*, that had only the output from executing the script, hello world, or whatever.
In python-mode v6, when I execute the same script, I get split window with a buffer that has a running python shell, with the output
Python 2.7.3 (default, Apr 19 2012, 00:55:09)
[GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
## executing temporary file /var/folders/
>>> Hello, world
The problem is that the v5 behavior is much more convenient, and I've gotten used to running scripts this way. Is there any way to set the behavior of v6 back to the way it was in v5?
Changed in python-mode: | |
status: | Fix Committed → Fix Released |
will introduce an option setting an one-for-all output buffer