[will-v-pi]

Use Python 3.12 with Zephyr, as later versions aren't supported - fixes #267

Fix link to docs - fixes #268

Add instructions to allow script execution for virtual environment - fixes #269

Fix argument passing to west build - fixes #270

[kvnloo]

A couple of things seem worth tightening before merge.

First, could we avoid recommending both:

Set-ExecutionPolicy RemoteSigned -Scope LocalMachine

and:

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

from an Administrator PowerShell?

LocalMachine is machine-wide and broader than the virtual-environment activation requirement. #269 explicitly raised least privilege as a concern.

If PowerShell activation is genuinely necessary, CurrentUser should normally be preferable. Better still, if the extension can invoke venv\Scripts\python.exe / west.exe directly, it shouldn't need to change PowerShell execution policy at all.

Second, showZephyrPythonNotFoundError() currently says:

Zephyr requires exactly Python 3.12 — other versions are not supported.

but the Linux fallback says Python 3.12 is strongly recommended and other versions may work. Could this be described as an extension compatibility pin instead?

Something like:

This extension uses Python 3.12 for the Zephyr environment because required packages may not be available on newer Python releases.

That seems more precise and avoids making a broader claim about every Zephyr configuration.

[will-v-pi]

A couple of things seem worth tightening before merge.

First, could we avoid recommending both:

Set-ExecutionPolicy RemoteSigned -Scope LocalMachine

and:

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

from an Administrator PowerShell?

LocalMachine is machine-wide and broader than the virtual-environment activation requirement. #269 explicitly raised least privilege as a concern.

If PowerShell activation is genuinely necessary, CurrentUser should normally be preferable. Better still, if the extension can invoke venv\Scripts\python.exe / west.exe directly, it shouldn't need to change PowerShell execution policy at all.

I've removed LocalMachine, as the Zephyr docs only require CurrentUser - I won't remove it entirely, as the Zephyr docs state it's necessary.

Second, showZephyrPythonNotFoundError() currently says:

Zephyr requires exactly Python 3.12 — other versions are not supported.

but the Linux fallback says Python 3.12 is strongly recommended and other versions may work. Could this be described as an extension compatibility pin instead?

Something like:

This extension uses Python 3.12 for the Zephyr environment because required packages may not be available on newer Python releases.

That seems more precise and avoids making a broader claim about every Zephyr configuration.

The Linux wording comes from the Zephyr docs, which state the 3.12 pin is only required on Windows, and is only strongly recommended otherwise.

Python 3.12 is strongly recommended. Using a newer Python release may fail on some systems, for example when installing the required packages on Windows.