Repository navigation
[Feature Request] Add a setting to disable specific environment managers #927
Description
Hello,
I create a new extension that adds micromamba support using your API: https://github.com/symzn/vscode-micromamba-env.
Currently, when an extension provides support for an environment type that is similar to a built-in one (like micromamba vs. conda), both managers can discover the same environments.
This leads to:
- Duplicate entries in the "Python: Select Interpreter" list.
- Potential user confusion about which environment source to use.
Proposed Solution
It could be great to have a new VS Code setting that allows users to specify a list of environment managers to disable.
Benefits
User Control: Empowers users to fully customize their environment toolchain.
Cleaner UI: Ensures a clean and de-duplicated list of Python interpreters.
Flexibility for Extension Authors: Allows specialized extensions (like for micromamba or pixi) to offer a seamless "replacement" experience for built-in managers.
Thank you for considering this proposal!
Activity
eleanorjboyd commentedon Oct 10, 2025
Hi! Thanks so much for creating this new extension, I can't wait to go try it out!
This is a good idea... some managers do interfere so we should have a way for users to fix this or specify.
Karthik Nadig (@karthiknadig) any thoughts here?
eleanorjboyd commentedon Oct 16, 2025
Hi symzn (@symzn) sorry for the delay here but we want to think through the problem holistically to make a good long term decision on this problem of overlapping. So we are working on this but don't have an update yet in what direction to go.
I have installed your extension and it is great! Ill look to figure out those few bugs you filed in addition to the feature request so thank you for filing them.
Thanks!
symzn commentedon Oct 17, 2025
Hello,
Thank you for your reply. Don't worry, I can lwait and live without this feature for a while.
Finally, the most critical issue preventing me from spreading the extension to others is the problem with the notebook kernel selection that does not propose micromamba's envs cf the bug I raise on select interpreter (I suppose that it could be the root cause).
Again Thanks!
github-actions commentedon Dec 12, 2025
Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.
abel1502 commentedon Mar 22, 2026
I'm also interested in this feature, but for a different reason. One of my installed applications maintains an isolated miniconda install, which I am not interested in ever using, but currently vs code detects it. This is particularly inconvenient because it stops the jupyter extension from choosing the system python automatically as the kernel.
github-actions commentedon Apr 24, 2026
This feature request has not received the 7 community upvotes needed to be considered for future planning within 60 days of its creation. We are closing this issue, but if the community rallies behind it in the future, we are happy to reconsider. Thank you for your feedback!
Happy Coding!