Package pyanaconda :: Module exception :: Class AnacondaExceptionHandler

Class AnacondaExceptionHandler

                  object --+    
                           |    
meh.handler.ExceptionHandler --+
                               |
                              AnacondaExceptionHandler

Instance Methods

[hide private]

handleException(self, (ty, value, tb), obj)
This is the main exception handling entry point.

source code

postWriteHook(self, (ty, value, tb), anaconda)
Subclasses may supply a function with this name that will be called immediately after the traceback is written to disk, but immediately before the UI is run.

source code

runDebug(self, (ty, value, tb))
This method is called when the "Debug" button is clicked.

source code

Inherited from meh.handler.ExceptionHandler: __init__, install, openFile, preWriteHook, runQuit, runSave

Inherited from meh.handler.ExceptionHandler (private): _setExitCode, _setExn

Inherited from object: __delattr__, __format__, __getattribute__, __hash__, __new__, __reduce__, __reduce_ex__, __repr__, __setattr__, __sizeof__, __str__, __subclasshook__

Class Variables

[hide private]

Inherited from meh.handler.ExceptionHandler: exitcode, exn

Properties

[hide private]

Inherited from object: __class__

Method Details

[hide private]

handleException(self, (ty, value, tb), obj)

source code

This is the main exception handling entry point. When Python gets an exception it doesn't know how to handle, this method will be called. It then saves the traceback and displays the main dialog asking the user what to do next. Once this method is called, there's no good way to go back to what you were doing before.

All arguments are passed in from the handler created by calling self.install(). This method should not usually be overridden by a subclass.

Overrides: meh.handler.ExceptionHandler.handleException: (inherited documentation)

postWriteHook(self, (ty, value, tb), anaconda)

source code

Subclasses may supply a function with this name that will be
called immediately after the traceback is written to disk, but
immediately before the UI is run.  This is to provide a place for
any special handling to happen once there is a file on disk.

(ty, value, tb) -- The Python objects created when a traceback
                   occurs.  These are passed in directly from
                   handleException.
obj -- A Python object that may be dumped to a file when the
       exception is saved.  This should be something like the top
       level object in a program.

Overrides: meh.handler.ExceptionHandler.postWriteHook: (inherited documentation)

runDebug(self, (ty, value, tb))

source code

This method is called when the "Debug" button is clicked. It may be overridden by a subclass if specialized behavior is required to enter debug mode.

Overrides: meh.handler.ExceptionHandler.runDebug: (inherited documentation)