Switch to non-deprecated Tools/wasm/wasi

[encukou]

Tools/wasm/wasi.py gave me a deprecation warning.

---

📚 Documentation preview 📚: https://cpython-devguide--1570.org.readthedocs.build/

[brettcannon]

Unfortunately it's a Python 3.15 thing, so the old instructions are necessary for 3.13 and 3.14. But since the location is practically the same I suspect people will notice and figure it out.

[hugovk]

Or shall we serve our users better and add version tabs like the macOS instructions here?

https://devguide.python.org/getting-started/setup-building/#macos

[encukou]

Here, I'd prefer a description of what changed. The alternatives are very similar and I might need both in a single session.

[brettcannon]

Here, I'd prefer a description of what changed. The alternatives are very similar and I might need both in a single session.

The only change is wasi/__main__.py vs. wasi.py. There's no functional difference right now and it was all done to make the files more manageable long-term (I would have backported to 3.14 but this was all part of my snafu when I accidentally committed to main right after the 3.14 branch was created).

[encukou]

So, right now, wasi.py works best for users?

Maybe 3.20 should be the version that starts showing the scary ⚠️ WARNING?

[brettcannon]

So, right now, wasi.py works best for users?

If "best" is "works for most people", then yes. But things will diverge more as time goes on anyway, e.g. adding externals support is hopefully coming in 3.15.

Maybe 3.20 should be the version that starts showing the scary ⚠️ WARNING?

That's an option. But this is also exactly the sort of thing no one will transition off of without some visible notice. And with it being infrastructure stuff, chances are it will take ages for people to notice.

[encukou]

If "best" is "works for most people", then yes. But things will diverge more as time goes on anyway, e.g. adding externals support is hopefully coming in 3.15.

So, as soon as those are in, the devguide should recommend wasi/. And have a note about 3.14 and below. Right?

I would have backported to 3.14 but this was all part of my snafu when I accidentally committed to main right after the 3.14 branch was created

There's a chance @hugovk would allow backporting a backwards-compatible infra change -- especially if the backport would omit the warning.

[hugovk]

Yeah, I think infra stuff like this is fine to backport.

[brettcannon]

So, as soon as those are in, the devguide should recommend wasi/. And have a note about 3.14 and below. Right?

Yes.

I think infra stuff like this is fine to backport.

👍