Fix Variables for python types with unexpected __qualname__ behavior #6364
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.
Addresses issue #6237
dfply.base.Intention
has a bad implementation of__getattr__
which impacts calls to built-in attributes such as__qualname__
. Instead of returning astr
it incorrectly returns a new instance ofIntention()
. This breaks our inspection logic and stopped Variables from working once objects of this type were encountered.This change adds some simple defensive code to the utility used by our Inspectors that summarize variables.
Added a simple unit test to cover this case.
Release Notes
New Features
Bug Fixes
__qualname__
return values do not stop Variables inspection. Fixes Variables pane does not refresh when variables are changed afterfrom dfply import *
#6237.QA Notes
Added a unit test to cover the general problem, but this fix covers the specific type mentioned in the customer issue.