"ModuleNotFoundError: No module named 'comm'" when running 'python -m ipykernel install'

Open

#1,225 opened on Mar 28, 2024 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: python
Domain: tooling

Research direction

Reproduce the failure with Python 3.10.14 and ipykernel 6.29.4 using the reported install command, then compare it with 6.29.3. Start at ipykernel/main.py, kernelapp.py, and ipkernel.py, and verify completion when the command installs the my-venv kernelspec at the reported Jupyter path.

Written by the indexing model from the issue text.

Description

Python version: 3.10.14
ipykernel version: 6.29.4

Command:

$ python -m ipykernel install --user --name=my-venv

Result:

Traceback (most recent call last):
  File "/opt/homebrew/Cellar/python@3.10/3.10.14/Frameworks/Python.framework/Versions/3.10/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/opt/homebrew/Cellar/python@3.10/3.10.14/Frameworks/Python.framework/Versions/3.10/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/Users/beise/[redacted]/.venv/lib/python3.10/site-packages/ipykernel/__main__.py", line 3, in <module>
    from ipykernel import kernelapp as app
  File "/Users/beise/[redacted]/.venv/lib/python3.10/site-packages/ipykernel/kernelapp.py", line 54, in <module>
    from .ipkernel import IPythonKernel
  File "/Users/beise/[redacted]/.venv/lib/python3.10/site-packages/ipykernel/ipkernel.py", line 15, in <module>
    import comm
ModuleNotFoundError: No module named 'comm'

Expected result:

Installed kernelspec my-venv in /Users/beise/Library/Application Support/Jupyter/kernels/my-venv

Works properly with v 6.29.3.

Dominant language: Python
Stars: 734
Forks: 411
Avg merge: 1d 2h
Merged PRs (30d): 9

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[essnmx] Fix typo in NXLauetof application definition Open

essnmx good first issue

Difficulty 1/5 Under an hour Newbie friendliness 95/100

scipp/ess#760 · Opened Sep 23, 2026
[Feature] 奇物选择添加优先级 Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

syfoud/Simulated_Scepter#174 · Opened Sep 23, 2026
garak adapter grades a NaN detector score as PASS Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

Giskard-AI/giskard-oss#2840 · 1 comment · Opened Sep 23, 2026
A claim comment carrying the issue number is silently declined while the workflow reports success Open

area: repo bug perceived difficulty: 2

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

Nitjsefnie-Harness-Commons/daedalus#926 · Opened Sep 23, 2026
`IOCExtractor` always fails: `ioc_analyzer.build()` takes 1 argument but the agent dispatcher passes 2 Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

yeti-platform/yeti#1380 · Opened Sep 23, 2026

More Python issues