You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there's an easier way to do ^ please let me know.
This will prevent joblib from triggering at all in the case that n_jobs is None. Much easier to debug parallel processing issues like #18 when I can enable/disable joblib entirely.
Happy to submit a PR for this!
The text was updated successfully, but these errors were encountered:
I think we should just default n_jobs to None, though I'm not sure it will change anything. From the joblib doc:
None is a marker for 'unset' that will be interpreted as n_jobs=1
(sequential execution) unless the call is performed under a
parallel_backend context manager that sets another value for
n_jobs.
Even when
n_jobs
is not passed, skope-rules still uses joblib as per the logs. This is becausen_jobs
defaults to 1 within theSkopeRules
class:skope-rules/skrules/skope_rules.py
Line 152 in e7f7b93
skope-rules/skrules/skope_rules.py
Line 169 in e7f7b93
skope-rules/skrules/skope_rules.py
Line 280 in e7f7b93
This should default to
None
and not be passed into theBaggingClassifier
andBaggingRegressor
if None to prevent triggering joblib. Something likeIf there's an easier way to do ^ please let me know.
This will prevent joblib from triggering at all in the case that
n_jobs
is None. Much easier to debug parallel processing issues like #18 when I can enable/disable joblib entirely.Happy to submit a PR for this!
The text was updated successfully, but these errors were encountered: