> > This is nice but breaking existing analysis scripts should be avoided. > > I suggest preserving the Analyzer class the way it is and adding a new > Analyzer2 class that follows the new method signature for trace event > methods.
You're right. This has too large effects on the API. I could go along with adding an Analyzer2 class. Should we mark Analyzer as deprecated then? We could make __init__ emit a warning, and say new features are only added to Analyzer2, but not put an exact EOL-date on Analyzer. I would rather not maintain two parallel implementations of the same. Let me know what you think.
