When following contributing docs on Windows "nox: The term 'nox' is not recognized"

[Tyriar]

Following https://github.com/microsoft/vscode-python/wiki/Coding#building I hit this:

I assumed that meant it's not on the PATH but was registered correctly as what normally happens on Windows, so I closed VS Code, opened it again (most people may know to try this) and created a new terminal (most people wouldn't know to do this step). But that didn't end up fixing it:

From there I had a screenshot of the warning above because I was reporting this issue, so I added it to the Windows environment by typing out the path manually:

After that nox was available.

I did then run into this error but I know that's about me ignoring Rust as a pre-requisite earlier.

We should explain that where nox is installed into may not be in the path. Also wasn't it meant to be installed into venv since it was activated?

[karthiknadig]

@Tyriar It looks like nox got installed in the wrong place. This is the typical Windows vs Unix issue with python virtual envs. python3 is valid in a activated venv only on Linux/Mac. Unless it was created using different environment manager tools like uv or virtualenv.

I have updated the docs to use the exact paths:

Windows:

Linux:

[Tyriar]

Thanks, I think that fixes the problem if .venv/bin/python is used directly. One thing though that you mention .venv/Scripts above when activating but not on the nox line. It's probably worth just splitting the latter part out into pwsh (windows) and sh (linux/mac) sections to simplify things.

[karthiknadig]

Done