[MRG] FIX Access Memory's location as a positional arg #11782
Closed
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.
I'm not sure why circle was failing claiming that
location
andcachedir
were both set. As far as I can tell, we never set both.However, we can set
cachedir
in old versions andlocation
in 0.12 by passing them as the first positional argument, rather than a named arg (which is slightly harder to read, but I think that it's still okay). Their semantics are identical as long asbackend
is the default.I have also avoided/changed some if-elses currently handling support of multiple joblib versions around this API change.
?Partial fix for #11771