def bye()sys exit( trybye(exceptprint('got it'print('continuing 'crucial errorabort nowoops--we ignored the exit python exiter py got it continuing you simply might not expect all the kinds of exceptions that could occur during an operation using the built-in exception classes of the prior can help in this particular casebecause the exception superclass is not superclass of systemexittrybye(except exceptionwon' catch exitsbut _will_ catch many others in other casesthoughthis scheme is no better than an empty except clause--because exception is superclass above all built-in exceptions except system-exit eventsit still has the potential to catch exceptions meant for elsewhere in the program probably worst of allboth using an empty except and catching the exception superclass will also catch genuine programming errorswhich should be allowed to pass most of the time in factthese two techniques can effectively turn off python' error-reporting machinerymaking it difficult to notice mistakes in your code consider this codefor examplemydictionary tryx myditctionary['spam'exceptx none continue here with oopsmisspelled assume we got keyerror the coder here assumes that the only sort of error that can happen when indexing dictionary is missing key error but because the name myditctionary is misspelled (it should say mydictionary)python raises nameerror instead for the undefined name referencewhich the handler will silently catch and ignore the event handler will incorrectly fill in none default for the dictionary accessmasking the program error moreovercatching exception here will not help--it would have the exact same effect as an empty excepthappily and silently filling in default and masking genuine program error you will probably want to know about if this happens in code that is far removed from the place where the fetched values are usedit might make for very interesting debugging task designing with exceptions