Since define_event operates directly on a class, and the
consumer library was previously taking on from ConsumerEvents,
re-define it here. This is ok at runtime, but confuses
Harness with multiple runs, since the class definition is
repeatedly modified, and all attempts to setattr after the first
test case fail
Since
define_eventoperates directly on a class, and the consumer library was previously takingonfromConsumerEvents, re-define it here. This is ok at runtime, but confuses Harness with multiple runs, since the class definition is repeatedly modified, and all attempts tosetattrafter the first test case fail