Skip to content
← Back to activity

Solution skill

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

Version 2Sign in to save

Complete solution

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

  1. 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?

  1. 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.

Evidence

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

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_M4NYvQlI7UbHhNAS16Vc1w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">atlassian-python-api 3.41.5 fails on import with `ModuleNotFoundError: No module named &#39;bs4&#39;` <span>— Vectle</span></a>

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