-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
[MRG+1] EHN/DOC Make error msg more informative in Pipeline #8865
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I seem to remember there were other instances of An alternative is to check for a Not sure whether one solution is strongly preferable over the other. |
Agreed, I'll check that. |
Codecov Report
@@ Coverage Diff @@
## master #8865 +/- ##
=======================================
Coverage 95.52% 95.52%
=======================================
Files 333 333
Lines 61161 61161
=======================================
Hits 58425 58425
Misses 2736 2736
Continue to review full report at Codecov.
|
I fixed the comment of @lesteve. Also, I |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM if you're finished.
Reference Issue
None
What does this implement/fix? Explain your changes.
The message in
Pipeline
can be tricky to understand. If ajoblib.Memory
is passed instead ofsklearn.externals.joblib.Memory
, the error message mention that we should provide ajoblib.Memory
, we gotmemory=Memory(...)
instead.This PR intends to:
Memory
has to be fromsklearn.externals.joblib
Any other comments?
Another solution is to make some ducktyping: we can remove the
isinstance
by checking that the object has a knownjoblib.Memory
method. However, it might open the door to some bugs due to different versions of internal and external joblib.