Closed billylaing closed 6 months ago
Hello, thanks for reporting this issue. For now, you'll have to pin joblib at < 1.3.0 as a workaround. We're working on updating civis-python for the recent joblib changes -- more to come!
Thanks. Y'all would probably know best based on usage and numbers of users installing, but this seems like a really good opportunity for a patch.
I'd be happy to make a PR to patch requirements.txt
until the more extensive updates for joblib changes lands. Thoughts?
Ah, I see, someone has already created one:
We've just released civis 1.16.1 on PyPI with joblib pinned at < 1.3.0, though I think we can leave this issue open since the 1.16.1 release was directly based off of 1.16.0 from Dec 2021 (we've started checking in API-breaking changes since 1.16.0). On the main
branch right now (at 34ed2de06f1151f5d4e10af121007efdd04178bf), this joblib issue is still outstanding.
Thanks @jacksonlee-civis
Appreciate the release!
Resolved by #467
Sorry, just saw @jacksonlee-civis 's comment about leaving this open for the main
branch! reopening.
Update: civis-python v2.3.0 is now available, where joblib is pinned at >= 1.3.0
.
With the latest release of joblib@1.3.1 the "my_exceptions" module was deprecated/removed.
This library is required by
civis@1.16.0
but will break ifjoblib
> 1.2 is installed.https://github.com/civisanalytics/civis-python/blob/34ed2de06f1151f5d4e10af121007efdd04178bf/requirements.txt#L6