-
Notifications
You must be signed in to change notification settings - Fork 414
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
FIX treat n_jobs=None as if left to its default value #1475
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #1475 +/- ##
==========================================
- Coverage 94.94% 94.88% -0.06%
==========================================
Files 45 45
Lines 7474 7491 +17
==========================================
+ Hits 7096 7108 +12
- Misses 378 383 +5
☔ View full report in Codecov by Sentry. |
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.
Indeed, thanks for the PR.
It's not fully fixed yet, i'm still working out some details |
Yes it is not fixed, it seems like we need to manage and test when |
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.
Better fix indeed! thanks @jeremiedbb 😁
just an extra nom regression test.
Actually, |
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, thx @jeremiedbb
I was quite surprised by the behavior of setting None
in the context but indeed, if this is what was enforced, I think it is a good idea to keep the same behavior.
Fixes #1473
Even if the new default value of
n_jobs
is a sentinel object, I think that we should not interpretn_jobs=None
as explicitely set because it used to mean 'unset'. Instead we should treat it identically as if it were left to its default value.