Full class/method names, max-width based column output, etc #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using the
inspect
module, we pull out anyself
method vars in a call and record that, and then resolve which class actually defines that method via line number.It changes the behavior slightly, in that overrides in the same module are no longer grouped together, but I found it much easier to understand, especially in summary view. The combination (as was the old behavior) is somewhat useful for stats view, but I still prefer this one.
As a result, the output is longer and less predictable, so I calculate the maximum width of each column and only output what is needed.
Also the .pyc file is removed.