### Feature or enhancement It should probably cover: - WASI version (`p1`, etc. as [done by Rust](https://bytecodealliance.zulipchat.com/#narrow/channel/394175-SIG-Guest-Languages/topic/Testing.20Python.20in.20wasi-libc.27s.20CI/near/613061764)) - Full WASI SDK version - Whether cooperative multithreading was compiled in `os.uname().machine` tells you whether it's wasm32 or 64, so this will be enough to calculate the host triple used for compiling. ### Has this already been discussed elsewhere? This is a minor feature, which does not need previous discussion elsewhere ### Links to previous discussion of this feature: https://bytecodealliance.zulipchat.com/#narrow/channel/394175-SIG-Guest-Languages/topic/Testing.20Python.20in.20wasi-libc.27s.20CI/near/612185469 <!-- gh-linked-prs --> ### Linked PRs * gh-159039 <!-- /gh-linked-prs -->
Activity
brettcannon commentedon Oct 2, 2026
https://discuss.python.org/t/not-using-structseq-in-sys/109328 is to discuss if not using structseq is okay.
brettcannon commentedon Oct 8, 2026
The discussion led to agreeing that using a namespace like
sys.implementationandsys.abi_infomade sense.pythonGH-158628: Implement `sys._wasi_info`
GH-158628: Implement `sys._wasi_info` (GH-159039)