Skip to content

Commit 0d473d8

Browse files
committed
PEP 11: Record WASI support
This is covered in PEP 816.
1 parent 7dd79b1 commit 0d473d8

1 file changed

Lines changed: 31 additions & 0 deletions

File tree

peps/pep-0011.rst

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -273,6 +273,37 @@ locale and cannot be reproduced in an appropriately configured non-ASCII
273273
locale will be closed as "won't fix".
274274

275275

276+
WASI
277+
''''
278+
279+
WASI support is defined in :pep:`816`.
280+
281+
====== ==== ========
282+
Python WASI WASI SDK
283+
====== ==== ========
284+
3.15 0.1 33
285+
3.14 0.1 24
286+
3.13 0.1 24
287+
3.12 0.1 21
288+
3.11 0.1 21
289+
====== ==== ========
290+
291+
All versions prior to Python 3.15 predate :pep:`816`. The version support for
292+
those earlier versions is based on what was supported when that PEP was
293+
written.
294+
295+
WASI was a tier 3 platform according to :pep:`11` for Python 3.11 and 3.12.
296+
WASI became a tier 2 platform starting with Python 3.13.
297+
298+
WASI 0.2 support has been skipped due to lack of time, to the point that it was
299+
deemed better to go straight to WASI 0.3 instead. This is based on a
300+
recommendation from the `Bytecode Alliance <https://bytecodealliance.org>`__.
301+
302+
WASI SDK 26 and 27 have a
303+
`bug <https://github.com/WebAssembly/wasi-libc/issues/617>`__ which causes
304+
CPython to hang in certain situations, and so they have been skipped.
305+
306+
276307
Unsupporting platforms
277308
======================
278309

0 commit comments

Comments
 (0)