feat: Make dump for fns, classes more stable and helpful #36188
Merged
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.
Description
This is a light iteration on #36162, making the
dump_settings
management command more helpful and stable for functions and classes.Supporting information
In particular, the
dump_settings
command currently prints out the rawrepr(...)
s for defined functions:In addition to being uninformative, these
at 0x123abc...
hashes change every run, so they appear in the diff as having "changed" every time.With this PR, here's what
dump_settings
will print out for functions:It will do something similarly helpful for classes and lambdas.
Deadline
Asap, as this unblocks several pending settings refactorings.