Enhancement: Automatic Python Environment Discovery

[Mohamed-Sobea]

I've identified a manual configuration bottleneck in client/src/extension.ts. Currently, the production mode relies on a hardcoded configuration:

const pythonPath = workspace.getConfiguration("Brian").get<string>("python.interpreterpath");
if (!pythonPath) { throw new Error(...); }

This requires users to manually set their path, which is difficult for researchers using Conda or virtual environments. I propose updating this to automatically detect the active VS Code Python interpreter using the ms-python.python extension API. This would make the extension Zero Config and much more robust.

[Mohamed-Sobea]

I encountered this friction personally while setting up my local development environment. It took some time to realize the extension required a manual path configuration to start the language server.

[mstimberg]

Hi @Mohamed-Sobea, yes I agree completely, this was actually what we meant with the first point in the GSoC project description: "Make the installation progress smooth and integrate with VS Code’s existing Python support". We mention the necessity to set the configuration at some point (https://github.com/brian-team/brian-code-editor/blob/main/brianextension/README.md#configurations), but it is very hidden (and well, shouldn't be necessary in the first place).

[Mohamed-Sobea]

Hi @Mohamed-Sobea, yes I agree completely, this was actually what we meant with the first point in the GSoC project description: "Make the installation progress smooth and integrate with VS Code’s existing Python support". We mention the necessity to set the configuration at some point (https://github.com/brian-team/brian-code-editor/blob/main/brianextension/README.md#configurations), but it is very hidden (and well, shouldn't be necessary in the first place).

Thanks for the clarification, Glad it matches the project direction. I will focus on automatic discovery in my gsoc proposal to support a smoother zero config experience.

[Mohamed-Sobea]

Hi Marcel @mstimberg,

I've started implementation for this issue. And I have a quick question:

Do you prefer that we unify the environment discovery for both Development and Production modes?

I reason that using the same logic for both states ensuresthat the Zero Config experience is fully tested during development. However, I want to make sure there isn't a specific reason why Development mode should remain isolated.

the current activate function, I noticed the logic is divided
// extension.ts export function activate(context: ExtensionContext): void { if (context.extensionMode === ExtensionMode.Development) { client = startLangServerTCP(2087); } else { const pythonPath = workspace.getConfiguration("Brian").get<string>("python.interpreterpath"); // ... launch logic } }

[Mohamed-Sobea]

Hi Marcel @mstimberg ,
The automatic environment discovery and the auto reload hook is ready over on the PR #19 .
Whenever you have time to review and close this issue 🙂

[mstimberg]

Hi @Mohamed-Sobea apologies for not replying earlier and many thanks for your PR – I will have a closer look tomorrow!