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.
This API is experimental in IPython 2.0, and may be revised in future versions.
Infrastructure for registering and firing callbacks on application events.
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.
This API is experimental in IPython 2.0, and may be revised in future versions.
Hover to see nodes names; edges to Self not shown, Caped at 50 nodes.
Using a canvas is more power efficient and can get hundred of nodes ; but does not allow hyperlinks; , arrows or text (beyond on hover)
SVG is more flexible but power hungry; and does not scale well to 50 + nodes.
All aboves nodes referred to, (or are referred from) current nodes; Edges from Self to other have been omitted (or all nodes would be connected to the central node "self" which is not useful). Nodes are colored by the library they belong to, and scaled with the number of references pointing them
