Note
This documentation is for a development version of IPython. There may be significant differences from the latest stable release (1.2.1).
Infrastructure for registering and firing callbacks on application events.
Unlike IPython.core.hooks, which lets end users set single functions to be called at specific times, or a collection of alternative methods to try, callbacks are designed to be used by extension authors. A number of callbacks can be registered for the same event without needing to be aware of one another.
The functions defined in this module are no-ops indicating the names of available events and the arguments which will be passed to them.
Note
This API is experimental in IPython 2.0, and may be revised in future versions.
Bases: object
Manage a collection of events and a sequence of callbacks for each.
This is attached to InteractiveShell instances as an events attribute.
Note
This API is experimental in IPython 2.0, and may be revised in future versions.
Initialise the CallbackManager.
Parameters: | shell
available_callbacks
|
---|
Register a new event callback
Parameters: | event : str
function : callable
|
---|---|
Raises: | TypeError
KeyError
|
Clear all callbacks for the given event.
Clear all callbacks for all events.
Call callbacks for event.
Any additional arguments are passed to all callbacks registered for this event. Exceptions raised by callbacks are caught, and a message printed.
Remove a callback from the given event.
Fires before code is executed in response to user/frontend action.
This includes comm and widget messages and silent execution, as well as user code cells.
Fires before user-entered code runs.
Fires after code is executed in response to user/frontend action.
This includes comm and widget messages and silent execution, as well as user code cells.
Fires after user-entered code runs.
Fires after initialisation of InteractiveShell.
This is before extensions and startup scripts are loaded, so it can only be set by subclassing.
Parameters: | ip : InteractiveShell
|
---|