Rename the routine to start the target running _start(), with a compatibility
routine start() calling it.

Some suites declare an event start(), which obscures this method, which
causes the class initializer to fail when called with start=1.

Based on bug report and fix suggestion by Jacob Kaplan-Moss.
1 file changed