Currently the build Python for Tools/wasm/wasi is put into build. That's fine, but if for some reason you are working with the same Python checkout across machines (e.g. in a container), it might be a bit confusing if you accidentally built in one place and then tried again later in another place. So using the actual build triple should help make it more obvious when that issue occurs.

Linked PRs

• GH-137484: Have Tools/wasm/wasi use the build triple instead of "build" #137485
• [3.14] GH-137484: Have Tools/wasm/wasi use the build triple instead of "build" (GH-137485) #137487