-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
Some TODOs for joblib 0.12.2 #11771
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
Comments
I think we need to remove all uses of cachedir...
|
I think the relevant joblib lines are, so this would still use I think leaving it to We might still might want to do some API change entry about this. |
I don't think we should worry too much about the default thing, at least
for now. However, it might be worth documenting the n_jobs=None semantics
in the Glossary entry on n_jobs.
|
So the final decision for (3) and (4) is to update the glossary and keep the doc? I won't argue about the decision but honestly I don't like it. Users will see |
At this stage, I'm a bit ambivalent.
…On 14 August 2018 at 13:38, Hanmin Qin ***@***.***> wrote:
So the final decision for (3) and (4) is to update the glossary and keep
the doc? I won't argue about the decision but honestly I don't like it.
Users will see n_jobs=None at the top of the doc and n_jobs : int,
optional (default=1) in parameters section, which might be confused.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#11771 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEz68AO8tTW_9OsPWICb1zgJfjfhydUks5uQkYygaJpZM4VyaQg>
.
|
Well as far as I see the other alternatives would be,
|
+1
We've updated the glossary, so we can refer to the glossary like what we've done for random_state. I prefer to update the doc accordingly, but I agree that this should not block the release. |
Closing given joblib 0.12.3. |
We introduce joblib 0.12.2 in #11741, but there're still some TODOs (open an issue for further discussion)
(1) Circle CI is failing
(2) We get many extra warnings in the examples
e.g.,
UserWarning: 'n_jobs' > 1 does not have any effect when 'solver' is set to 'liblinear'. Got 'n_jobs' = None.
(3) In the doc, we still have things like
n_jobs : int, optional (default=1)
(4) Maybe add some explanations about the difference between
n_jobs=1
andn_jobs=None
?The text was updated successfully, but these errors were encountered: