It was pretty useless, it just printed a message and sat there and waited for the user to hit enter.

It didn't feel like it belonged in a top-level framework.  If a particular application wants this functionality, it is a 2 line change to add it back.

This command is explicitly for running Python script files within an embedded Python interpreter.

The advantages over the py command with "run" are:
- Tab-completion of file system paths is supported
- Command-line arguments can be passed to the Python script

The extra functionality of listing a span (slice) of history items present in the list command has been incorporated into the existing history command and the list command has been removed.

Unit tests have been updated accordingly.

In the process a bug was fixed that was causing a crash if and end was supplied to the span but not a start.

Added a list of commands to explicitly exclude displaying in the help menu of commands which detailed help can be retrieved for.

By default, only "do_eof" is in this list since that isn't a command which is ever intended for an end user to directly enter on the command line.

Also updated unit tests to reflect new default help menu.

The out-of-the-box help menu now looks a lot cleaner:
- All redundant command aliases have been removed
(NOTE: They can still be used if self.abbrev is True, which is the default)
- All previously undocumented commands have been documented
- Unit tests and README.rst documentation has been updated to reflect new behavior