[Idle-dev] IDLE interpreter window

[Dirk-Ulrich Heise]

David Scherer:
>This is an artefact of the way Idle runs programs in its own interpreter.
>Once a module is imported, it stays imported until you explicitly reload
it,
>even across multiple runs.
>
>Moving to a model where the user program executes in a separate process
>addresses this and many other problems.

Do you mean that every time the user fixes an error in one of the modules,
he would have to reload the whole project? This would increase
the turn around time. IMHO, one should find a way to exploit the dynamism
of Python by just reloading the changed functions into the right namespaces.
(Maybe this could be an option for advanced users, but it can save a lot
of time in larger projects. It's possible via setattr.)
Would this be possible with a separate process for the user program?

Admittedly, sometimes you lose control, so an explicit reset (forcing a
full reload) would be a needed function.

Dirk