-
-
Notifications
You must be signed in to change notification settings - Fork 860
Switch to non-deprecated Tools/wasm/wasi #1570
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
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. |
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 |
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 |
So, right now, Maybe 3.20 should be the version that starts showing the scary |
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.
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. |
So, as soon as those are in, the devguide should recommend
There's a chance @hugovk would allow backporting a backwards-compatible infra change -- especially if the backport would omit the warning. |
Yeah, I think infra stuff like this is fine to backport. |
Yes.
👍 |
Tools/wasm/wasi.py
gave me a deprecation warning.📚 Documentation preview 📚: https://cpython-devguide--1570.org.readthedocs.build/