joerick
Refactor to track information other than just time
Supercedes #166.
This refactor allows pyinstrument to collect information other than the code object that was executing during the profiling. Currently, this function is only used for the class name, but I've got plans to capture other information.
Because the extra information ('attributes') isn't part of the identifier, it can vary between invocations. This was important for the class name, where the 'self' variable could change at runtime, while the same frame was executing. But this will also allow tracking of the currently executing line number, which unlocks the ability for pyinstrument to have line-by-line profiling, as well as tree-style profiling.
Ah. Now there is a problem with the class name resolution on CPython 3.11! Two steps forward, one step back...
The 3.11 support is firmed-up. I think I'm ready to go with this. I might just do a little extra testing to make sure there are no perf regressions.
Just a note, this is merged into master but wasn't part of the 4.3.0 release, I wanted to hold this feature since it might warrant a 5.0.0 release...