Multibuffer mayhem

[bugree]

Python mode 6.1.1 opens up temporary buffers and displays them as soon as a buffer evaluation fails. This leads to several opened buffers, all with similar contents. I found myself several times editing some temporary files instead my own source file

[Andreas Roehler (a-roehler)]

Am 30.03.2013 17:42, schrieb bugree:
> Public bug reported:
>
> Python mode 6.1.1 opens up temporary buffers and displays them as soon
> as a buffer evaluation fails. This leads to several opened buffers, all
> with similar contents. I found myself several times editing some
> temporary files instead my own source file
>

Need some more info. May you send some example code, which triggers the bug?
How the buffers displayed are named then?

[bugree (moritz-tacke)]

Any error, e.g.

def do_something():
wrong_indent

Now invoking
C-c !
C-c C-c

On Sat, 30 Mar 2013, Andreas Roehler wrote:

> Am 30.03.2013 17:42, schrieb bugree:
>> Public bug reported:
>>
>> Python mode 6.1.1 opens up temporary buffers and displays them as soon
>> as a buffer evaluation fails. This leads to several opened buffers, all
>> with similar contents. I found myself several times editing some
>> temporary files instead my own source file
>>
>
> Need some more info. May you send some example code, which triggers the bug?
> How the buffers displayed are named then?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1162272
>
> Title:
> Multibuffer mayhem
>
> Status in An Emacs mode for editing Python code:
> New
>
> Bug description:
> Python mode 6.1.1 opens up temporary buffers and displays them as soon
> as a buffer evaluation fails. This leads to several opened buffers,
> all with similar contents. I found myself several times editing some
> temporary files instead my own source file
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/python-mode/+bug/1162272/+subscriptions
>

[bugree (moritz-tacke)]

This behavior is triggered by some errors at evaluation, but does not
appear constantly.

When trying to evaluate (C-c C-c) the following:

import os
hhhh

def do_something():
wrong_indent

emacs jumps to a newly created buffer, the minibuffer states:

Jumping to exception in file /tmp/python-118568UC.py on line 8

On Sat, 30 Mar 2013, Andreas Roehler wrote:

> Am 30.03.2013 17:42, schrieb bugree:
>> Public bug reported:
>>
>> Python mode 6.1.1 opens up temporary buffers and displays them as soon
>> as a buffer evaluation fails. This leads to several opened buffers, all
>> with similar contents. I found myself several times editing some
>> temporary files instead my own source file
>>
>
> Need some more info. May you send some example code, which triggers the bug?
> How the buffers displayed are named then?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1162272
>
> Title:
> Multibuffer mayhem
>
> Status in An Emacs mode for editing Python code:
> New
>
> Bug description:
> Python mode 6.1.1 opens up temporary buffers and displays them as soon
> as a buffer evaluation fails. This leads to several opened buffers,
> all with similar contents. I found myself several times editing some
> temporary files instead my own source file
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/python-mode/+bug/1162272/+subscriptions
>

[Andreas Roehler (a-roehler)]

Am 30.03.2013 19:38, schrieb bugree:
> Any error, e.g.
>
> def do_something():
> wrong_indent
>
> Now invoking
> C-c !
> C-c C-c
>

Okay, see the error should point at the original buffer,
not at the temporary file - which is executed in reality...

BTW you must not call py-shell first, C-c C-c should work right from the spot.

Thanks for the report.