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?

Add instructions for older versions

bf9e6bd

Copy link

Member Author

encukou commented Jun 7, 2025

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

Copy link

Member

brettcannon commented Jun 9, 2025

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).

Copy link

Member Author

encukou commented Jun 10, 2025

So, right now, wasi.py works best for users? Maybe 3.20 should be the version that starts showing the scary ⚠️ WARNING?

Copy link

Member

brettcannon commented Jun 10, 2025

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.

Copy link

Member Author

encukou commented Jun 11, 2025

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.

Merge branch 'main' into tools-wasm-wasi

086d4a0

Copy link

Member

hugovk commented Jun 11, 2025

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

Copy link

Member

brettcannon commented Jun 11, 2025

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. 👍

brettcannon mentioned this pull request Jun 12, 2025

Reorganize WASI-related files in Tools/wasm python/cpython#133600

Open

willingc approved these changes Jun 15, 2025

View reviewed changes

AA-Turner approved these changes Jun 15, 2025

View reviewed changes

Hide details View details AA-Turner merged commit b062cc9 into python:main Jun 15, 2025

4 checks passed

Copy link

Collaborator

willingc commented Jun 16, 2025

python/cpython#133600 landed?

Copy link

Member

brettcannon commented Jun 16, 2025

python/cpython#133600 landed? It would have been convenient, but now I have a bit of motivation to get that issue closed this week. 😅

❤️ 1 willingc reacted with heart emoji

encukou deleted the tools-wasm-wasi branch June 17, 2025 06:05

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

brettcannon brettcannon approved these changes

willingc willingc approved these changes

AA-Turner AA-Turner approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

None yet

Follow Lee on X/Twitter - Father, Husband, Serial builder creating AI, crypto, games & web tools. We are friends :) AI Will Come To Life!

Check out: eBank.nz (Art Generator) | Netwrck.com (AI Tools) | Text-Generator.io (AI API) | BitBank.nz (Crypto AI) | ReadingTime (Kids Reading) | RewordGame | BigMultiplayerChess | WebFiddle | How.nz | Helix AI Assistant

5 participants

Footer

© 2025 GitHub, Inc.

Footer navigation

• Terms
• Privacy
• Security
• Status
• Docs
• Contact
• Manage cookies
• Do not share my personal information

Follow Lee on X/Twitter - Father, Husband, Serial builder creating AI, crypto, games & web tools. We are friends :) AI Will Come To Life!

Check out: eBank.nz (Art Generator) | Netwrck.com (AI Tools) | Text-Generator.io (AI API) | BitBank.nz (Crypto AI) | ReadingTime (Kids Reading) | RewordGame | BigMultiplayerChess | WebFiddle | How.nz | Helix AI Assistant

[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.

👍

[willingc]

python/cpython#133600 landed?

[brettcannon]

python/cpython#133600 landed?

It would have been convenient, but now I have a bit of motivation to get that issue closed this week. 😅