ImportError: cannot import name 'joblib' from 'sklearn.externals'

Not specified by the original author.

TL;DR: scikit-learn 0.23 removed its vendored joblib. Change from sklearn.externals import joblib to plain import joblib (install it if missing).

The error

ImportError: cannot import name 'joblib' from 'sklearn.externals'

Fix it

1. Replace the import:

   import joblib

   Expected: no import error.

2. If joblib is not installed:

   pip install joblib

3. Verify:

   python -c "import joblib; print(joblib.__version__)"

   Expected: prints a version.

When this applies

Use this when old code or tutorials do from sklearn.externals import joblib on scikit-learn 0.23+.

When it does not apply

If the error names a different sklearn.externals member (like six), that vendored copy is gone too; find its standalone package. If sklearn itself will not import, reinstall it.

Compatibility

scikit-learn 0.23+. Plain import joblib works on every sklearn version.

Root cause

sklearn used to vendor joblib under sklearn.externals. In 0.23 the vendored copy was dropped and joblib became a proper declared dependency, so the old import path no longer exists.

Edge cases

Old pickles saved with sklearn.externals.joblib still load fine with standalone joblib. If a requirements file pins ancient sklearn, upgrading sklearn is better than working around the import.

GitHub issue mosh-hamedani/python-supplementary-materials#1 reports ImportError: cannot import name 'joblib' from 'sklearn.externals' with a modern scikit-learn. The verified fix: sklearn 0.23 removed the vendored sklearn.externals.joblib, so the import becomes plain import joblib (installing the standalone joblib package if needed), which works on all sklearn versions. Full thread: https://github.com/mosh-hamedani/python-supplementary-materials/issues/1

Not specified by the original author.

TL;DR

Check your version of Azure AI Search first , maintainers often fix the underlying bug in a later release, and the thread may predate it. The import error comes from a version mismatch between the two packages, so upgrade or downgrade them together instead of one at a time.

Steps

1. Pin the pair the reporter confirmed working: langchain==0.1.8 with azure-search-documents==11.4.0. The import error comes from a version mismatch between the two packages, so upgrade or downgrade them together instead of one at a time.
2. This comes from one real issue thread (https://github.com/Azure/azure-sdk-for-python/issues/34341); it is the verified fix or approach from that thread, not a general manual. Check your version of Azure AI Search first , maintainers often fix the underlying bug in a later release, and the thread may predate it.

When to use

You are seeing this: Pin the pair the reporter confirmed working: langchain==0.1.8 with azure-search-documents==11.4.0. Use this skill when you run into "ImportError: cannot import name 'ExhaustiveKnnAlgorithmConfiguration' from 'azure.search.documents.indexes.models".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: langchain 0.1.8, azure-search-documents 11.4.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/Azure/azure-sdk-for-python/issues/34341

Issue gh:Azure/azure-sdk-for-python#34341 asked: Issue Azure/azure-sdk-for-python#34341 (closed, 16 comments): hi hope you doing well . i am using specific version of sdk but it didnot work this time dont know why? `--------------------------------------------------------------------------- ImportError Traceback (most recent call last) Cell In[7], [line 5](vscode-notebook-cell:?execution_count=7&line=5) [1](vscode-notebook-cell:?execution_count=7&line=1) # embeddings: OpenAIEmbeddings = OpenAIEmbeddings(deployment="embed-002", chunksize=1) [4](vscode-notebook-cell:?executioncount=7&line=4) indexname = "saa" ----> [5](vscode-notebook-cell:?executioncount=7&line=5) vector_store: AzureSearch = AzureSe The verified answer from the thread: Pin the pair the reporter confirmed working: langchain==0.1.8 with azure-search-documents==11.4.0. The import error comes from a version mismatch between the two packages, so upgrade or downgrade them together instead of one at a time. Source: https://github.com/Azure/azure-sdk-for-python/issues/34341

Not specified by the original author.

TL;DR

For "ImportError: cannot import name 'Mistral' from 'mistralai'": check which Python your notebook kernel uses with sys.executable and compare it to which pip, then reinstall with python -m pip install mistralai using that exact interpreter. Restart the Jupyter kernel after reinstalling so it picks up the new package.

ImportError: cannot import name 'Mistral' from 'mistralai'

Steps

1. Importing the client failed with ImportError: cannot import name 'Mistral' from 'mistralai' even though the package appeared installed. The reporter had installed mistralai with conda, which gave the old 0.x release, and then with pip, which gave 1.x, and was running the code inside a Jupyter notebook. The maintainer could not reproduce it with a clean setup, which pointed at the environment rather than the package. Restarting the Jupyter kernel so it picked up the pip-installed 1.x package made the import work.
2. This import error almost always means your interpreter is loading a different mistralai than you think, commonly the old 0.x from conda when pip installed 1.x. Check which Python your notebook kernel uses with sys.executable and compare it to which pip, then reinstall with python -m pip install mistralai using that exact interpreter. Restart the Jupyter kernel after reinstalling so it picks up the new package. The reporter in this case just needed the kernel restart once the right version was in place.

When to use

You are seeing this: The maintainer could not reproduce it with a clean setup, which pointed at the environment rather than the package. Use this skill when you run into "ImportError: cannot import name Mistral from mistralai after mixing conda and pip installs".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Question: Importing the client failed with ImportError: cannot import name 'Mistral' from 'mistralai' even though the package appeared installed. The reporter had installed mistralai with conda, which gave the old 0.x release, and then with pip, which gave 1.x, and was running the code inside a Jupyter notebook. The maintainer could not reproduce it with a clean setup, which pointed at the environment rather than the package. Restarting the Jupyter kernel so it picked up the pip-installed 1.x package made the import work.

Verified resolution: This import error almost always means your interpreter is loading a different mistralai than you think, commonly the old 0.x from conda when pip installed 1.x. Check which Python your notebook kernel uses with sys.executable and compare it to which pip, then reinstall with python -m pip install mistralai using that exact interpreter. Restart the Jupyter kernel after reinstalling so it picks up the new package. The reporter in this case just needed the kernel restart once the right version was in place. Source: https://github.com/mistralai/client-python/issues/211

Thread: https://vectle.com/threads/thr_gdmokGmfY3t-HLB3o6mwuA