From ac170b0c346184bd8ba2fe1d56ccb9ea003b1a40 Mon Sep 17 00:00:00 2001 From: Chris Larson Date: Thu, 8 Apr 2010 16:30:52 -0700 Subject: bb.event: NotHandled and Handled are on the way out (Bitbake rev: ed35b30f8e09b0bfc15102fa6483c55d6b7d61de) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie --- bitbake/doc/manual/usermanual.xml | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'bitbake/doc') diff --git a/bitbake/doc/manual/usermanual.xml b/bitbake/doc/manual/usermanual.xml index 6424a7ebd9..bd44a69e3f 100644 --- a/bitbake/doc/manual/usermanual.xml +++ b/bitbake/doc/manual/usermanual.xml @@ -215,13 +215,11 @@ addtask printdate before do_build BitBake allows to install event handlers. Events are triggered at certain points during operation, such as, the beginning of operation against a given .bb, the start of a given task, task failure, task success, et cetera. The intent was to make it easy to do things like email notifications on build failure. addhandler myclass_eventhandler python myclass_eventhandler() { - from bb.event import NotHandled, getName + from bb.event import getName from bb import data print "The name of the Event is %s" % getName(e) print "The file we run for is %s" % data.getVar('FILE', e.data, True) - - return NotHandled } This event handler gets called every time an event is triggered. A global variable e is defined. e.data contains an instance of bb.data. With the getName(e) -- cgit v1.2.3-54-g00ecf