attributeerror: module 'jwt' has no attribute 'encode'

Not specified by the original author.

TL;DR

attributeerror: module 'jwt' has no attribute 'encode' means Python imported the wrong package: the abandoned jwt distribution on PyPI shadows the real one, PyJWT, and it has no encode function. Fix it by running pip uninstall -y jwt PyJWT and then pip install PyJWT. Also check you do not have a local file named jwt.py shadowing the installed package, then verify with a one-line jwt.encode call.

AttributeError: module 'jwt' has no attribute 'encode'

Use this when

• import jwt succeeds but jwt.encode raises AttributeError: module 'jwt' has no attribute 'encode'
• pip show jwt reports an installed distribution (that is the wrong one)
• jwt.__file__ points at a small package with no encode or decode in it
• The code worked on another machine or in another virtualenv with the same requirements file

Not for this skill when

• The error is ModuleNotFoundError: No module named 'jwt'. Nothing is installed at all; see the related skill below
• The error names a different module or a different missing attribute (for example module 'jwt' has no attribute 'decode' after a PyJWT 1.x to 2.x upgrade is a different, API-change problem)
• jwt.encode exists but raises a type or algorithm error. Import is fine then; the call arguments are the problem

Steps

1. See which distribution you actually have. Run:

pip show jwt
pip show PyJWT
python -c "import jwt; print(jwt.__file__)"

Expected: if pip show jwt finds a package, that is the wrong one. PyJWT alone should be the only jwt provider.

2. Remove both distributions and install the right one:

pip uninstall -y jwt PyJWT
pip install PyJWT

Expected: pip reports PyJWT installed and no jwt distribution remaining.

3. Rule out a shadowing local file:

ls jwt.py

If a jwt.py exists in your working directory, rename it and delete the pycache folder next to it, because Python imports the local file before site-packages.

Expected: no jwt.py in the working directory, or the renamed file no longer shadows the import.

4. Verify the fix in the same environment that raised the error:

python -c "import jwt; print(jwt.encode({'a': 1}, 'secret', algorithm='HS256'))"

Expected: a three-part token string prints, with no AttributeError.

Variant phrasings

module 'jwt' has no attribute 'encode'

The short form of the same error, often pasted without the AttributeError prefix. Same wrong-package cause and the same uninstall-then-PyJWT fix in steps 1 to 2.

pyjwt encode attributeerror

Usually the same collision seen from the other side: the code expects PyJWT (import jwt, jwt.encode) but the environment has the jwt distribution installed. Work steps 1 to 2.

jwt has no attribute encode after pip install jwt

Installing with pip install jwt is exactly how the wrong package gets in. The package you want is named PyJWT even though it imports as jwt.

attributeerror module jwt has no attribute decode

Same collision, hit on the decode call instead of encode. The abandoned jwt package lacks both; steps 1 to 2 fix decode too.

Root cause

PyPI hosts two different distributions that both import as jwt: the real PyJWT and an unrelated, long-abandoned jwt package. Installing the wrong one is common because pip install jwt looks right, and the symptom is always this AttributeError: import succeeds, encode is missing. A local file named jwt.py causes the identical symptom by shadowing the installed package.

Edge cases

• Virtualenv mismatch: pip and python point at different environments, so the fix lands where the code does not run. Re-run step 1 with the exact python that raises the error.
• Both distributions installed at once: uninstall both (step 2) before reinstalling, or leftover files from the wrong one can survive a plain pip install PyJWT.
• Pinned requirements: if a requirements file lists jwt, change the line to PyJWT or the wrong package comes back on the next install.

Tool compatibility

PyJWT 2.x on Python 3. The squatter jwt distribution is unmaintained and should never be installed. Steps shown for pip; with conda or uv, uninstall and install the same two distribution names.

Related skills

• ModuleNotFoundError: No module named 'jwt' (nothing installed at all, the neighbouring failure): https://vectle.com/skills/sklxlSmzgPDYhERSmqcvsU-Q
• ModuleNotFoundError: No module named 'Crypto' (the same wrong-or-missing package shape in pycryptodome): https://vectle.com/skills/skl_yYUlQSrr4W6sVcUbM3piAQ
• importerror: import openpyxl failed (a missing companion package rather than a wrong one): https://vectle.com/skills/skl_tju-YKpJbVtEA6pRwyCBUw

Provenance

Built from the itsourcecode fix guide and the project reports linked in the evidence.

PyPI hosts two different distributions that both import as jwt: the real PyJWT and an unrelated, long-abandoned jwt package. Installing the wrong one is extremely common because pip install jwt looks right, and the symptom is always this AttributeError. The itsourcecode fix guide documents the exact uninstall-both-then-install-PyJWT remedy, the officecurtains project hit it in production with the same fix, and a Medium build log describes losing 45 minutes to it. A local file named jwt.py causes the identical symptom by shadowing the installed package.

Not specified by the original author.

ImportError: cannot import name 'encode' from partially initialized module 'jwt'

TL;DR: a file named jwt.py in your project shadows PyJWT. Rename your file, delete pycache, and the import works. Check with python -c "import jwt; print(jwt.__file__)": if it points at your project, that file is the culprit.

ImportError: cannot import name 'encode' from partially initialized module 'jwt' (most likely due to a circular import)

The fix

1. Confirm the shadowing:

python -c "import jwt; print(jwt.__file__)"

Success check: the path is under site-packages. If it is your project folder, keep going.

2. Rename jwt.py to something descriptive like token_utils.py and fix any local imports of it.
3. Clear bytecode:

rm -rf __pycache__ jwt.pyc

4. Verify:

python -c "from jwt import encode; print('ok')"

Expected output: ok.

Agent? Search Vectle for more: curl -s 'https://vectle.com/api/v1/search?q=pyjwt+partially+initialized+module'

When this applies

• The error says "partially initialized module 'jwt'".
• The same code works from any other directory.
• You have a jwt.py somewhere on sys.path.

When it does NOT apply

• The error is AttributeError about a missing encode, which is the wrong-package problem.
• The error is No module named 'jwt', which means PyJWT is not installed.

Why this happens

The script directory comes first on sys.path, so a local jwt.py wins over site-packages. Python starts importing your file, your file (or something it triggers) does from jwt import encode, and the half-built local module has no encode yet. Never name project files after third-party top-level packages.

Compatibility

All Python and PyJWT versions. The trigger is the filename.

A file named jwt.py in the working directory shadows the installed PyJWT package: Python imports the local file first, and from jwt import encode then fails with the partially-initialized-module ImportError because the local file is still being imported. The itsourcecode troubleshooting guide for the jwt encode failures explicitly calls out checking for a local jwt.py via checking jwt.file as the second fix after the wrong-package uninstall. Renaming the file and clearing pycache resolves it immediately.

Not specified by the original author.

ModuleNotFoundError: No module named 'jwt'

TL;DR: the import is jwt but the pip package is PyJWT. Run python -m pip install PyJWT. If it is already installed, your pip and python are different interpreters; python -m pip fixes that too.

ModuleNotFoundError: No module named 'jwt'

The fix

1. Install with the same interpreter that runs your code:

python -m pip install PyJWT
python -c "import jwt; print(jwt.__version__)"

Success check: prints a version like 2.8.0.

2. If it says already satisfied but the import still fails, you have two Pythons:

python -c "import sys; print(sys.executable)"
python -m pip show PyJWT | grep Location

The Location must sit under the same prefix as sys.executable. If not, reinstall into the right one with python -m pip.

3. If you need RSA/ECDSA support, install the crypto extra: python -m pip install "PyJWT[crypto]".

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

When this applies

• import jwt fails right after a fresh clone or in a new venv/CI container.
• A tutorial told you to pip install jwt, which installs an unrelated dead package.

When it does NOT apply

• ImportError: cannot import name 'PyJWT' from 'jwt': you have a shadowing file or ancient version; different fix.
• jwt.exceptions.ExpiredSignatureError or decode errors: the import works, your token or call is wrong.
• python-jose users: that package imports as jose, not jwt.

Tool and version compatibility

PyJWT 2.x, Python 3.7+. PyJWT 1.x is ancient; upgrade.

Why it happens

PyPI name and import name differ: pip install PyJWT gives you import jwt. There is also a squatter package literally named jwt that does nothing useful. Installing the wrong one, or installing into a different interpreter than the one running the code, produces exactly this error.

Edge cases

• A file named jwt.py in your project shadows the package; rename it.
• If both jwt and PyJWT show in pip list, uninstall jwt.
• In Docker, make sure the pip install happens in the same layer/stage that runs the app.

The question of why No module named 'jwt' appears on startup even though JWT auth was configured is documented in real project troubleshooting guides. The verified fix: the import is jwt but the pip package is PyJWT, so pip install PyJWT (using python -m pip to match the interpreter). Source: https://github.com/pocheang/payguard-crew/blob/HEAD/docs/guides/TROUBLESHOOTING.md, thread gh:pocheang/payguard-crew troubleshooting.