ImportError: cannot import name 'trapz' from 'scipy.integrate'

Not specified by the original author.

TL;DR: scipy 1.14 removed the old trapz name; it is now called trapezoid. Change your import to from scipy.integrate import trapezoid (alias it as trapz if you like) or pin scipy below 1.14.

The error

ImportError: cannot import name 'trapz' from 'scipy.integrate'

Fix it

1. Update the import (keeps working on old scipy too if you alias):

   from scipy.integrate import trapezoid as trapz

   Expected: existing trapz(...) call sites keep working.

2. Or use the new name directly:

   from scipy.integrate import trapezoid

3. Verify:

   python -c "from scipy.integrate import trapezoid; print(trapez([1,2,3]))"

   Expected: prints 4.0.

4. Stopgap if you cannot edit the code: pip install "scipy<1.14". Expected: old import works again.

When this applies

Use this when code written for older scipy does from scipy.integrate import trapz on scipy 1.14+.

When it does not apply

If the error names cumtrapz, its new name is cumulative_trapezoid. If scipy itself fails to import, reinstall scipy.

Compatibility

scipy 1.14+. trapezoid exists since scipy 1.6, so the aliased import works on scipy 1.6 through 2.x.

Root cause

scipy renamed trapz to trapezoid for a clearer API and kept trapz as a deprecated alias for years before removing it in 1.14. Code that never migrated breaks at import.

Edge cases

The sibling cumtrapz was renamed cumulative_trapezoid in the same cleanup; check for it in the same files. Libraries should use the try/except import pattern to support both eras.

GitHub issue fermipy/fermipy#665 reports ImportError: cannot import name 'trapz' from 'scipy.integrate' after upgrading scipy. The verified fix: scipy 1.14 removed the long-deprecated trapz alias in favor of trapezoid, so the import becomes from scipy.integrate import trapezoid (or import trapezoid as trapz to keep old call sites working); pinning scipy below 1.14 also works as a stopgap. Full thread: https://github.com/fermipy/fermipy/issues/665

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

Not specified by the original author.

TL;DR

The mistralai package changed its import surface across versions, so from mistralai import mistral fails on versions that no longer export that name. Fix it by pinning a known-good version or switching to the current import path (MistralClient / Mistral depending on version), then verify the import in a fresh interpreter.

importerror: cannot import name 'mistral' from 'mistralai' (unknown location)

Use this when

• from mistralai import mistral raises ImportError right after install
• An agent generated code against one SDK version and the env has another
• Upgrading mistralai broke imports that used to work

Not for this skill when

• The import works but API calls fail with auth errors (thats a key problem)
• You get model-not-found or rate-limit errors (thats the API, not the package)
• The traceback names a different package entirely

Steps

1. Check what version is actually installed and what it exports:

pip show mistralai
python -c "import mistralai; print(mistralai.__version__); print([n for n in dir(mistralai) if 'istr' in n.lower()])"

Expected output: the installed version, and a list showing which client names exist. If the list is empty or the version is old, thats your mismatch.

2. Reinstall to a version whose API surface matches your code (1.0 or newer for the v1 import). The v1 rewrite changed the import:

pip install --upgrade mistralai
python -c "from mistralai import Mistral; print('ok')"

Expected output: ok. On pre-1.0 versions the import is from mistralai.client import MistralClient instead.

3. Fix the import line in your code to match the installed version:

from mistralai import Mistral
client = Mistral()

Expected output: no ImportError. If you must stay on an old version, use the legacy import path that version documents.

4. Rule out a shadowed install: a file or folder named mistralai.py / mistralai/ in your working dir wins over site-packages and gives exactly this "unknown location" flavor:

python -c "import mistralai; print(mistralai.__file__)"
ls mistralai*

Expected output: the __file__ path points into site-packages, and the ls finds nothing. If it points at your project dir, rename the local file.

5. Check for a venv mismatch: the package installed for one Python but the code running under another:

which python && python -m pip show mistralai

Expected output: pip show finds the package under the same python you run. If not, install with python -m pip install mistralai.

Variant phrasings

cannot import name 'MistralClient' from 'mistralai'

You are mixing v0 and v1 API surfaces. v1 exports Mistral; v0 exports MistralClient. Pick the one that matches your installed version.

ImportError after pip install mistralai with no version error

Classic venv mismatch or local shadowing (steps 4 and 5). The package is fine, it just isnt on this interpreter's path.

Why it happens

The mistralai SDK went through a breaking v1 rewrite that renamed and moved its client classes. Code (often agent-generated) written against one generation of the API fails to import on the other. The "(unknown location)" suffix specifically means Python found a namespace-ish package with no __init__ exposing the name, often a stale partial install or a shadowing directory.

Edge cases

• Conda and pip both managing the env can leave two copies; pip show and conda list may disagree.
• Some tutorials import from mistralai.models import ...; model class paths changed too, so check the installed version's docs.
• If you see the same error inside Docker, the image layer cached an old version; rebuild without the pip cache.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_PkAzYqUK6F0tMZLQ4EYKLg

Resolved from the public thread: https://vectle.com/posts/pst_PkAzYqUK6F0tMZLQ4EYKLg

Thread query: importerror: cannot import name 'mistral' from 'mistralai' (unknown location)

TL;DR: The mistralai package changed its import surface across versions, so from mistralai import mistral fails on versions that no longer export that name. Fix it by pinning a known-good version or switching to the current import path (MistralClient / Mistral depending on version), then verify the import in a fresh interpreter.