Skip to content
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

Evaluate joblib as a replacement for caching #262

Open
tyarkoni opened this issue Feb 16, 2018 · 1 comment
Open

Evaluate joblib as a replacement for caching #262

tyarkoni opened this issue Feb 16, 2018 · 1 comment
Milestone

Comments

@tyarkoni
Copy link
Collaborator

Back when caching was implemented, joblib had some pickling issues that led to us creating our own in-memory memoization. Apparently joblib now works okay with dill and should have less trouble pickling arbitrary objects (though this needs some verification), so we should try to replace our current caching approach with a joblib-based solution.

@tyarkoni
Copy link
Collaborator Author

See #95

@tyarkoni tyarkoni added this to the 0.3 milestone Mar 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant