[Idle-dev] More on saving files

[Guido van Rossum]

> You're right about the desirability of this "as though" behavior, including
> the edit buffers for any modules that I happen to have open at the moment.
> However, just sending the edit buffers to the loader program wouldn't do
> everything that I like so much about your current version of IDLE, namely
> that whenever I run I know for sure that my most recent edits have been
> saved permanently to disk and don't reside solely in memory buffers. I have
> come to really appreciate the sense of security that comes from knowing
> that this successful run corresponds to the program on disk. I want the
> combination of saving to ".new" with passing the edit buffers to the loader.

What happened to the idea of producing a (temporary?) fork of IDLE at
SourceForge to get more people to work on these things?

I can't offer to participate, but I don't want to stifle development
either!

--Guido van Rossum (home page: http://www.pythonlabs.com/~guido/)