Different Kernels for Same venv Name

Open
#1,132 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
jupyter, python
Domain
tooling

Research direction

No files, tests, or specific entry points are identified. Reproduce the issue by creating kernels from same-named venvs in two directories, then trace the kernel-creation behavior; done means both kernels remain available with their distinct display names and venv references.

Written by the indexing model from the issue text.

Description

Issue:
Let's say I have a venv called "env" in Directory A, and also another venv elsewhere with the same name "env" in Directory B. If I create a new kernel (display-name = "Kernel A") in Directory A based on the first "env", then try to create a separate kernel (display-name = "Kernel B") in Directory B based on the second "env," I noticed that only the second kernel is kept. It seems to overwrite the Kernel A, perhaps since both are based on a venv with the same name "env."

I haven't done too much digging, and since I'm still exploring much of the functionalities of ipykernel, I may have missed something here.

Is there a way to create a separate kernel with a different display-name that references different venvs that use the same name?

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

Contributor guide

Open the contributing guide

First steps

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

More from ipython/ipykernel

All issues in ipython/ipykernel

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.