[trac384] addressed two comments from jeremy
- only set a prompt if we have an interactive terminal - be a bit less verbose on errors in case of a socket error, only print that error, and not the extra (is it running?) message. FailToLogin() exception is no longer printed (the methods that raise it already print the real error themselves) Unexpected Exceptions are now printed *more* verbose, i.e. with a full stacktrace instead of just a message. If we want to 'expect' more error types (and only print a short message that speaks for itself, to look more userfriendly), we should add those explicitely, and not use 'except Exception'.
Showing with 18 additions and 18 deletions