Open
Description
🚀 Feature Request
Currently, when a user selects "Create Python Environment" inside the Jupyter kernel selection UI, they can only create the environment in the workspace root directory. However, sometimes users want to create the environment in a custom directory.
💡 Proposed Solution
- After selecting "Create Python Environment", allow users to specify a directory before proceeding with
venv
orconda
. - The default can still be the workspace root, but users should have the flexibility to change it.
🤔 Why is this needed?
- Some projects require virtual environments in custom locations.
- Prevent workspace clutter.
- Aligns with flexibility offered in the VS Code Python extension.
📌 Steps to Reproduce
- Open a Jupyter notebook in VS Code.
- Click "Select Kernel" > "Select Another Kernel".
- Choose "Python Environment" > "Create Python Environment".
- Currently, VS Code forces the environment to be created in the workspace root.
🔄
- Manually creating a venv/conda environment and selecting it later (not user-friendly and currently it can not be automatically detected).