Description

brettcannon

opened on Oct 2, 2026

Issue body actions

Feature or enhancement

It should probably cover:

• WASI version (p1, etc. as done by Rust)
• 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

Linked PRs

• GH-158628: Implement sys._wasi_info #159039

Activity

1. brettcannon

   added

   type-featureA feature request or enhancementA feature request or enhancement

   OS-wasi

   on Oct 2, 2026
2. brettcannon commented on Oct 2, 2026

   

   brettcannon

   on Oct 2, 2026

   MemberAuthor

   More actions

   https://discuss.python.org/t/not-using-structseq-in-sys/109328 is to discuss if not using structseq is okay.
3. StanFromIreland

   added

   interpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)

   on Oct 3, 2026
4. brettcannon commented on Oct 8, 2026

   

   brettcannon

   on Oct 8, 2026

   MemberAuthor

   More actions

   The discussion led to agreeing that using a namespace like sys.implementation and sys.abi_info made sense.
5. brettcannon

   self-assigned this

   on Oct 8, 2026
6. brettcannon

   added 2 commits that reference this issue on Oct 13, 2026

   pythonGH-158628: Implement `sys._wasi_info`

   9140c56

   GH-158628: Implement `sys._wasi_info` (GH-159039)

   084aff8
7. brettcannon

   closed this as completedon Oct 15, 2026

Issue actions