You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: peps/pep-NNNN.rst
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,13 +23,13 @@ Motivation
23
23
24
24
CPython has supported WASI according to :pep:`11` since Python 3.11.
25
25
As part of this support, CPython needs to target two different things: the WASI_ version and the `WASI SDK`_ version (both of whose development is driven by the `Bytecode Alliance`_).
26
-
The former is the specification of WASI itself while the latter is a version of clang_ with wasi-libc_ as the sysroot that allows for compiling CPython to WASI.
26
+
The former is the specification of WASI itself while the latter is a version of clang_ with a specific version of wasi-libc_ as the sysroot that allows for compiling CPython to WASI.
27
27
There is roughly an annual release cadence for new WASI versions while there's no set release cadence for WASI SDK.
28
28
29
-
Agreeing on the WASI and WASI SDK version to support allows for clear targeting of the CPython code base towards those versions.
29
+
Agreeing on which WASI and WASI SDK versions to support allows for clear targeting of the CPython code base towards those versions.
30
30
This lets the community set appropriate expectations as to what will (not) be considered a bug if it only manifests itself under a different WASI or WASI SDK version.
31
31
It also provides the community an overall target for WASI and WASI SDK for any specific Python version when building other software like libraries.
32
-
This is important as WASI SDK is NOT forwards- or backwards-compatible, making broad coordination important so code works together.
32
+
This is important as WASI SDK is NOT forwards- or backwards-compatible in the ABI it produces, making broad coordination important so code works together.
33
33
34
34
35
35
Rationale
@@ -38,7 +38,7 @@ Rationale
38
38
[What do we have to consider when coming up with a spec?]
39
39
40
40
While technically separate, CPython cannot support a version of WASI until WASI SDK supports it.
41
-
WASI versions are considered backwards-compatible with each other, but WASI SDK is NOT compatible forwards or backwards.
41
+
WASI versions are considered backwards-compatible with each other, but WASI SDK is NOT compatible forwards or backwards in terms of the ABI it produces.
42
42
As such, it's important to set support expectations for a specific WASI SDK version in CPython.
43
43
Historically, the support difference between WASI SDK versions for CPython have involved settings in the ``config.site`` file that is maintained for WASI.
44
44
Support issues have come up due to bugs in WASI SDK itself.
0 commit comments