[MRG] Fix builtin PrettyPrinter usage on estimators #12938
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.
Reference Issues/PRs
Fixes #12906
What does this implement/fix? Explain your changes.
This PR makes a copy of the
_dispatch
dict in_EstimatorPrettyPrinter
to prevent the builtinPrettyPrinter
class to directly call_EstimatorPrettyPrinter._print_estimator
on estimator objects, which fails since_print_estimator
assumes the object is an instance of_EstimatorPrettyPrinter
with specific attributes.Any other comments?
Note that even when only
PrettyPrinter
is used, estimators will still be rendered with_EstimatorPrettyPrinter
sincePrettyPrinter
internally usesrepr()
which itself uses_EstimatorPrettyPrinter
.So using
PrettyPrinter
or_EstimatorPrettyPrinter
on an estimator has the exact same effect.