ImportError+cannot+import+name+bool+from+numpy

Not specified by the original author.

How to fix ImportError: cannot import name 'bool' from 'numpy'

Stop importing the alias. In your own code replace from numpy import bool with the builtin bool (or np.bool_ if you need the numpy scalar type). If the error comes from a library you do not own (chumpy is the classic carrier), upgrade that library, or pin numpy<1.24 as a stopgap. numpy 1.24 removed the old aliases np.bool, np.int, np.float and friends for good.

The exact error

ImportError: cannot import name 'bool' from 'numpy'

Fix it

1. Find the bad import: grep -rn "from numpy import" --include=*.py . and look for bool, int, float, complex, object, unicode, str. Expected: you see the exact line raising the error

2. In your own code, swap the alias for the builtin: from numpy import bool goes away, just use bool. Only keep numpy's np.bool_ if you truly need the numpy scalar. Expected: import succeeds on numpy>=1.24

3. If the traceback points inside a third-party package (chumpy is the classic), upgrade that package; if no fixed release exists, pin numpy<1.24 in your requirements. Expected: pip shows numpy 1.23.x and the import works

When this applies

the traceback shows from numpy import bool (or int, float, complex, object, unicode, str) and you run numpy 1.24 or newer

When this does NOT apply

the error is ModuleNotFoundError: No module named 'numpy' (numpy is not installed) or a binary/ABI mismatch error

Versions

numpy >= 1.24, Python 3.8+

Why it happens

numpy deprecated these aliases in 1.20 and removed them in 1.24. Old code and old libraries still import them.

Edge cases

np.bool_ still exists and is fine to use. Pinning numpy<1.24 is a band-aid; the real fix is updating the importing code.

Asked about: ImportError: cannot import name 'bool' from 'numpy' (gh:jxyjxyw/stereo-inertial-poser (README known-issues)). The verified fix: Stop importing the alias. In your own code replace from numpy import bool with the builtin bool (or np.bool_ if you need the numpy scalar type). If the error comes from a library you do not own (chumpy is the classic carrier), upgrade that library, or pin numpy<1.24 as a stopgap. numpy 1.24 removed the old aliases np.bool, np.int, np.float and friends for good. Full thread: https://github.com/jxyjxyw/stereo-inertial-poser/blob/HEAD/README.md

Not specified by the original author.

TL;DR: VisibleDeprecationWarning was removed in numpy 2.0, so from numpy import VisibleDeprecationWarning cannot work anymore. Replace it with Python's builtin warnings module. If you cannot change the code, pin numpy below 2.0 as a stopgap.

The error

ImportError: cannot import name 'VisibleDeprecationWarning' from 'numpy'

Fix it

1. Find every place the removed name is imported:

   grep -rn "VisibleDeprecationWarning" [your project dir]

   Expected: a list of files doing from numpy import VisibleDeprecationWarning.

2. Replace the import with the stdlib warnings module:

   import warnings

   and where the code raised or filtered it, use warnings.warn(msg, DeprecationWarning) or the builtin DeprecationWarning class. Expected: no remaining references to the numpy import.

3. Re-run the import that failed. Expected: it imports cleanly.

4. If you cannot edit the code (a pinned third-party package), downgrade numpy instead:

   pip install "numpy<2.0"

   Expected: the old import works again.

When this applies

Use this when the traceback points at from numpy import VisibleDeprecationWarning and numpy 2.x is installed.

When it does not apply

If the error names a different removed symbol (np.float, np.unicode_, np.asfarray), each needs its own replacement. If numpy is still 1.x, something else is wrong.

Compatibility

numpy 2.0 and later. VisibleDeprecationWarning existed through numpy 1.26.

Root cause

NumPy 2.0 did a long-planned cleanup of deprecated names. VisibleDeprecationWarning was a thin subclass of UserWarning, so the stdlib warnings module plus DeprecationWarning is the intended replacement.

Edge cases

Some libraries vendored the name; upgrading the library to a numpy-2-compatible release is better than patching. If tests filter on the warning class, update the filter to DeprecationWarning too.

A user running numpy 2.0.2 hit ImportError: cannot import name 'VisibleDeprecationWarning' from 'numpy' when importing a package whose code did from numpy import VisibleDeprecationWarning. The verified answer: numpy 2.0 removed VisibleDeprecationWarning along with other deprecated names, so the import must go. The accepted fix was replacing it with Python's builtin warnings module (import warnings and use DeprecationWarning), which the reporter confirmed fixed the numpy 2.0 issues. Full thread: https://github.com/llnl/qnd/issues/17

Not specified by the original author.

TL;DR

IPython 9 removed the old ipython.core.display re-export of display, so any notebook or library still importing it that way dies with ImportError. Change the import line to from IPython.display import display (same for HTML, Image, Markdown). Then grep the repo for other ipython.core.display imports so the next cell does not hit the same wall.

ImportError: cannot import name 'display' from 'ipython.core.display'

Use this when

• A notebook cell fails with ImportError naming ipython.core.display right after an IPython upgrade.
• The traceback points at a library file that does from ipython.core.display import display or HTML.
• You recently upgraded IPython past 8.x and old notebooks broke.

Not for this skill when

• The error is ModuleNotFoundError for ipykernel. That is a missing kernel package, a different fix.
• The kernel itself dies or segfaults. That is a binary/ABI problem, not an import path.

Steps

1. Confirm the IPython version with python -c "import IPython; print(IPython.__version__)". Verify: you see 9.x, where the old path is gone.
2. Find every old-style import: grep -rn "ipython.core.display" --include=*.py --include=*.ipynb .. Verify: you have the full list of files to change.
3. Replace from ipython.core.display import display with from IPython.display import display in each file. Verify: a fresh python -c "from IPython.display import display" imports cleanly.
4. Restart the kernel and re-run the failing cell top to bottom. Verify: no ImportError and outputs render.
5. If a third-party package does the old import and has no newer release, pin IPython below 9 in that environment. Verify: the package imports again in a fresh kernel.

Variant phrasings

importerror cannot import name display from ipython core display

The same failure with the ImportError prefix. Identical fix.

cannot import display from IPython after upgrade

The post-upgrade search phrasing. Same root cause, same one-line import change.

ipython.core.display deprecated

The historical framing. In current IPython the path is removed, not just deprecated.

Compatibility: IPython 8.x and 9.x. The from IPython.display import ... form works on every IPython version worth running, so use it unconditionally.

Why it happens

IPython moved its display helpers to the top-level IPython.display package years ago and kept ipython.core.display as a compatibility re-export. IPython 9 dropped that shim.

Edge cases / pitfalls

• Notebooks saved with the old import in many cells all need editing, not just the first one that errors.
• Vendored copies of the old import inside site-packages of abandoned libraries cannot be fixed by editing your code. Pin IPython or patch the library.

Provenance

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

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

Thread query: "cannot import name 'display' from 'ipython.core.display'"

TL;DR: IPython 9 removed the old ipython.core.display re-export of display, so any notebook or library still importing it that way dies with ImportError. Change the import line to from IPython.display import display (same for HTML, Image, Markdown). Then grep the repo for other ipython.core.display imports so the next cell does not hit the same wall.