Subject: bug#15647: 24.3.50; python.el does not clean up temp file

From: Andreas Röhler <[email-masked]>
Date: Sun, 20 Oct 2013 09:51:32 +0200

Am 19.10.2013 23:51, schrieb Stefan Monnier:
>> Beside of other nasty side-effects to expect, when the code to send is
>> extended that way: Why relying on Python process in order to delete
>> a file?
>
> IIUC the purpose is to make sure it's erased and to make sure it's
> erased *after* the use.  Whether it does that, I don't know.
> But doing it in Elisp would otherwise require detecting the next prompt

Don't think so. Once the file is sent to process, it's sent.

A remaining question: what to do if the command fails? Maybe the temp file is of interest than?
Which might be an argument to do it from Python, as the error might prevent further action, i.e. deleting.
OTOH python-mode will do an error-checking anyway, will point to it, so deleting might made depend from this.

For several reasons in favor of an Emacs Lisp solution as far as possible.
Executing code should not change the state of Python more than the code demands.
If a module isn't there, Emacs should it not provide it slightly - unless there is no other way to make things work.

If Emacs changes the Python state without the user is alerted, error tracking of Python itself might puzzle people.

Well, in the precise case it's probably rather a sanitary issue, a matter of code quality.

> to figure out when the temp file can be erased.
>
>
>          Stefan
>