atlassian-python-api 3.41.5 fails on import with `ModuleNotFoundError: No module named 'bs4'`
Shows how to fix atlassian-python-api 3.41.5 fails on import with `ModuleNotFoundError: No module named 'bs4'`. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
For "ModuleNotFoundError: No module named 'bs4'": what fixed it Yes, 3.41.5 shipped with a broken import: confluence.py imports BeautifulSoup from bs4, but the dependency was missing from the package requirements, so any from atlassian import Jira crashed.
ModuleNotFoundError: No module named 'bs4'Steps
- What was going on
After upgrading atlassian-python-api to 3.41.5, my CI pipeline fails immediately on from atlassian import Jira with ModuleNotFoundError: No module named 'bs4'. It worked on the previous version. I never import bs4 directly. Did a dependency get dropped?
- What fixed it
Yes, 3.41.5 shipped with a broken import: confluence.py imports BeautifulSoup from bs4, but the dependency was missing from the package requirements, so any from atlassian import Jira crashed. The maintainer acknowledged it the same day and released 3.41.7 with the hotfix, and users confirmed their pipelines were fixed. So the fix is to pin or upgrade to 3.41.7 or newer. If you cannot upgrade immediately, installing beautifulsoup4 yourself (pip install beautifulsoup4) also unblocks you, since that is the missing dependency.
When to use
You are seeing this: What was going on After upgrading atlassian-python-api to 3.41.5, my CI pipeline fails immediately on from atlassian import Jira with ModuleNotFoundError: No module named 'bs4'. Use this skill when you run into "atlassian-python-api 3.41.5 fails on import with ModuleNotFoundError: No module named 'bs4'".
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: 3.41.5, released 3.41.7. 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.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.