Skip to content

Commit 9e3781a

Browse files
committed
Tweak some wording
1 parent bc92ba8 commit 9e3781a

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

peps/pep-NNNN.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,13 +23,13 @@ Motivation
2323

2424
CPython has supported WASI according to :pep:`11` since Python 3.11.
2525
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.
2727
There is roughly an annual release cadence for new WASI versions while there's no set release cadence for WASI SDK.
2828

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.
3030
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.
3131
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.
3333

3434

3535
Rationale
@@ -38,7 +38,7 @@ Rationale
3838
[What do we have to consider when coming up with a spec?]
3939

4040
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.
4242
As such, it's important to set support expectations for a specific WASI SDK version in CPython.
4343
Historically, the support difference between WASI SDK versions for CPython have involved settings in the ``config.site`` file that is maintained for WASI.
4444
Support issues have come up due to bugs in WASI SDK itself.

0 commit comments

Comments
 (0)