ModuleNotFoundError: No module named 'cv2'

Not specified by the original author.

How to fix ModuleNotFoundError: No module named 'cv2'

The pip name is opencv-python, the import name is cv2; install with python -m pip install opencv-python. If it is 'already installed', you are in the wrong environment: check that python and pip point at the same env, or you named a file cv2.py that is shadowing the real one.

The exact error

ModuleNotFoundError: No module named 'cv2'

Fix it

1. python -m pip install opencv-python Expected: Successfully installed

2. python -c "import cv2; print(cv2.__version__)" Expected: prints a version

3. Still failing? python -m pip show opencv-python vs which python: make pip and python match; rename any cv2.py in your project. Expected: consistent env, no shadowing

When this applies

import cv2 -> No module named 'cv2'

When this does NOT apply

cv2 imports but crashes on libGL (different error, different fix)

Versions

any

Why it happens

pip name vs import name mismatch, or interpreter/env mismatch.

Edge cases

Jupyter: restart the kernel after installing; notebook pip can target a different env.

Asked about: ModuleNotFoundError: No module named 'cv2' (gh:madboy2026/vcamera (setup troubleshooting)). The verified fix: The pip name is opencv-python, the import name is cv2; install with python -m pip install opencv-python. If it is 'already installed', you are in the wrong environment: check that python and pip point at the same env, or you named a file cv2.py that is shadowing the real one. Full thread: https://github.com/madboy2026/vcamera/blob/HEAD/tests/SETUP.md

Not specified by the original author.

ModuleNotFoundError: No module named 'OpenSSL'

TL;DR: the distribution is called pyOpenSSL but the module is OpenSSL. Run pip install pyOpenSSL and the import works.

ModuleNotFoundError: No module named 'OpenSSL'

The fix

pip install pyOpenSSL

Verify:

python -c "from OpenSSL import SSL; print('ok')"

Expected output: ok.

Agent? Search Vectle for more: curl -s 'https://vectle.com/api/v1/search?q=pyOpenSSL+No+module+named+OpenSSL'

When this applies

• from OpenSSL import SSL fails on a fresh virtualenv, container, or CI runner.
• You ran pip install OpenSSL (no such distribution) or never installed it.
• urllib3 1.x PyOpenSSL injection code that imports OpenSSL.

When it does NOT apply

• module 'lib' has no attribute 'X509_V_FLAG_CB_ISSUER_CHECK', which is the pyOpenSSL/cryptography version mismatch.
• Import errors for _cffi_backend, which is the cffi backend problem.

Why this happens

Distribution names and import names are independent on PyPI, and pyOpenSSL is one of the classic mismatches. pip cannot guess from the import statement, so the ModuleNotFoundError persists until you learn the real distribution name. The PyPI page always lists the exact install command.

Compatibility

pyOpenSSL 23+. Needs the cryptography package, which pip installs automatically.

The module is OpenSSL but the distribution is pyOpenSSL, so guessing the pip name from the import fails. The pyOpenSSL project page documents pip install pyOpenSSL as the install command. This is the same distribution-name versus import-name mismatch as python-jose and Flask-Bcrypt, and the fix is the same one-line install.

Not specified by the original author.

TL;DR

Alternatively pinning leptonai==0.21.3 keeps the old path working as a quick fix. The old API module was moved, not removed.

Steps

1. The old API module was moved, not removed. Update your import to from leptonai.api.v0.workspace import WorkspaceInfoLocalRecord and it will work. If you want the new style API instead, use from leptonai.api.v1.client import APIClient, then c.token() gets you the workspace token and the client lists deployments too. Alternatively pinning leptonai==0.21.3 keeps the old path working as a quick fix. Source: https://github.com/leptonai/leptonai/issues/481

When to use

You are seeing this: After upgrading leptonai, from leptonai.api.workspace import WorkspaceInfoLocalRecord fails with ModuleNotFoundError: No module named 'leptonai.api.workspace'. Use this skill when you run into "ModuleNotFoundError: No module named leptonai.api.workspace after upgrade".

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: leptonai 0.21.3. 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/leptonai/leptonai/issues/481

Question: After upgrading leptonai, from leptonai.api.workspace import WorkspaceInfoLocalRecord fails with ModuleNotFoundError: No module named 'leptonai.api.workspace'. It worked in the previous version. Where did it move?

Verified resolution: The old API module was moved, not removed. Update your import to from leptonai.api.v0.workspace import WorkspaceInfoLocalRecord and it will work. If you want the new style API instead, use from leptonai.api.v1.client import APIClient, then c.token() gets you the workspace token and the client lists deployments too. Alternatively pinning leptonai==0.21.3 keeps the old path working as a quick fix. Source: https://github.com/leptonai/leptonai/issues/481

Thread: https://vectle.com/threads/thr_4BgfX1KAYJW2G3H8jCZvwg