Python 3 is killing Python

[Rick Johnson]

[A missed point from my last reply...]

Terry Reedy said:
> I believe there is a proposal to be able to clear the
> shell window. We just need to add "Clear and restart
> shell".

A command that allows a user to clear the *ENTIRE* "shell
IO" and *ALSO* resets the global and local symbol tables
*WITHOUT* requiring a re-start of the IDLE application,
would be a great addition indeed!

Currently "IDLE shell" has *ONLY* the "Restart Shell"
command, which simply resets the symbol table whilst leaving
all previous "shell IO" untouched. Which is useful in some
situations, but not all...

    CONSIDER,

Sometimes you just want to remove the displayed result of
the *LAST* command executed *WHILST* maintaining any
previous displayed "shell IO" -- for instance, in the case
of accidentally printing a *very large* data structure, or a
horrendously untrimmed "dir()" requests.

    ############################################################
    #        DISAMBIGUATION: "EditUndo" vs "OutputUndo"        #
    ############################################################
    # In order to prevent confusion with the typical "edit-    #
    # undo" of "CONTROL+Z", we should refer to the action of   #
    # "remove the last output displayed" as an "output-undo".  #
    ############################################################

To solve this dilemma in *MY* command shell, i use the
"ALT+UP_ARROW" to delete everything from the "last command
prompt" up to "the end of the text buffer", in effect,
creating an "output-undo" command without *DEFILING* the
standard semantics of ubiquitous "CONTROL+Z".

I think IDLE needs all three functionality of:

  1. Reset symbol tables *WHILST* retaining previous "shell
  IO" (Already exists via "Shell->Restart Shell")

  2. Reset symbol tables *AND* clear all "shell IO" (Maybe:
  "Shell->Reset Shell")

  3. Remove the displayed result of the *LAST* command
  processed. (Maybe: "Shell->Remove Last Output")

Hotkeys for all three are a must and should be configurable
by the user.

> There is also an idea to put help output in an
> output window.

I believe more windows just creates more confusion for the
user. Sometimes you have no choice but to add additional
"views" to a GUI interface, however, in this case at least,
i believe a menu command (coupled with a keyboard event) is
a best solution to maintain the highest level of "interface
manageability" -- IMHO.