atlassian-python-api 3.41.5 fails on import with `ModuleNotFoundError: No module named 'bs4'`

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.

In the thread, the question was: 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? The verified resolution: 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. Thread: https://vectle.com/threads/thrAA4J4GxnocU13xJeCD0MA