build: use call command when calling python

[ZenMasterJacob20011]

When running .\vcbuild.bat in PowerShell the file is stopping execution after calling python configure %configure_flags% even if python configure exits with a status of 0. Because the commands after python configure %configure_flags% are never called you don't finish building and thus never get a out or release folder with node.exe in it.
I am currently developing on Windows 10 and it looks like using call python configure %configure_flags% allows batch to continue after the python subroutine is finished

[StefanStojanovic]

I do not think this is required. When I run .\vcbuild.bat from PowerShell, it executes normally and finishes the build. Are you sure this is not some problem with your local setup?

[ZenMasterJacob20011]

Could be... Adding a video just to show that without the call python it doesn't continue execution after calling python. I am currently using pyenv for windows to manage my python versions. Going to see if maybe that's the problem. I'll also paste below some of the specs of my local setup

OS: Windows 10
Python: 3.13.2
PowerShell: 5.1.19041.6328
Additionally I am not using python that you get from the Microsoft Store like it says in BUILDING.MD but am using pyenv for windows to manage python versions.

Desktop.2025.10.06.-.10.23.04.08.mp4

[marco-ippolito]

I experience the same problem described in the issue, thanks for fixing it!

[gurgunday]

Not sure if request-ci is needed here? Please correct me if I'm wrong

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/69596/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/69636/

[StefanStojanovic]

Additionally I am not using python that you get from the Microsoft Store like it says in BUILDING.MD but am using pyenv for windows to manage python versions.

This is the main difference between my setup and yours. btw @marco-ippolito, since you're also seeing this, do you use the same Python setup?

Since the build passed in the CI, I'm OK with the change. Failures are most likely flakes, so I've restarted the failed jobs.

[marco-ippolito]

Additionally I am not using python that you get from the Microsoft Store like it says in BUILDING.MD but am using pyenv for windows to manage python versions.

This is the main difference between my setup and yours. btw @marco-ippolito, since you're also seeing this, do you use the same Python setup?

Since the build passed in the CI, I'm OK with the change. Failures are most likely flakes, so I've restarted the failed jobs.

Yes I use pyenv for windows

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/69638/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/69704/

[nodejs-github-bot]

Landed in 94cbb77

[ShenHongFei]

Because pyenv places .pyenv\pyenv-win\shims\python.bat at the beginning of the PATH, it effectively replaces the direct invocation of python.exe. As a result, when a batch script executes python ... without using call, the script transfers control to python.bat and does not return to the original script after python.bat finishes—since python.bat is itself a batch file, and calling another .bat/.cmd file directly in a batch script causes execution to jump to that file without returning. Therefore, to ensure that the script resumes execution after running Python, you must use call python ... in .bat files when using pyenv on Windows.

However, if pyenv is not in use and the python command resolves directly to python.exe (a true executable, not a .bat or .cmd script), then both with and without call behave identically: the batch script will always continue executing after the python.exe process terminates. This is because invoking an .exe file from a batch script does not transfer control permanently—it simply launches the executable as a subprocess and waits for it to finish before proceeding. In this case, call python ... and python ... have the same effect.

@ZenMasterJacob20011 @marco-ippolito