Stefan Hajnoczi writes: > Only one point: please don't introduce PUBLIC yet. Let's add it when > it's needed. At the moment nothing uses it.
> I have tested this series with all backends and looked at the diff > between the old tracetool and tracetool.py. > I'm happy with this series. We need to test it hard for 1.1 to make > sure there are no hickups for tracing users. Sure. I'll send v4 without the PUBLIC-related contents and turning "kwargs" into specific arguments. Once accepted, I'll send the first two batches of changes in my queue, which are orthogonal to instrumentation (basically tracing cleanups in both the build and the API). I suppose everyone prefers to wait until after the 1.1 release to start having a look at instrumentation (which I still have to port to this new tracetool). Lluis -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth
