GH-109975: Copyedit 3.13 What's New: New Features

[AA-Turner]

A copy-editing pass for new features. Next will be other language changes.

Summary of changes:

• Move the free-threaded and JIT sections up, though still below pyrepl/improved error messages, as these two will have high end-user impact
• Update the pyrepl descriptions as Windows is now supported and readline isn't required.
• Update snippets for error messages to not promote putting multiple statements on one line
• Significantly update the "free-threaded" section
• Consolidate and update the JIT section.
  • Is What's New the right place for the fairly detailed description of the Tier 2 architecture / configure options? I note that --enable-experimental-jit isn't mentioned anywhere else in the docs.
• Move __static_attributes__ to other language changes (just a copy/paste)
• Rewrap to 80 chars.

As @hugovk mentioned in #109975 (comment), there isn't a great place to link to for the macOS installers currently. I'm not best placed to write that guide though, given I've never owned a Mac!

A

• Issue: What's New in Python 3.13 (copyediting) #109975

---

📚 Documentation preview 📚: https://cpython-previews--122990.org.readthedocs.build/en/122990/whatsnew/3.13.html#new-features

[hugovk]

@colesbury Please could you check the free-threaded section?

https://cpython-previews--122990.org.readthedocs.build/en/122990/whatsnew/3.13.html#free-threaded-cpython

---

• Consolidate and update the JIT section.

  • Is What's New the right place for the fairly detailed description of the Tier 2 architecture / configure options? I note that --enable-experimental-jit isn't mentioned anywhere else in the docs.

Let's ask @brandtbucher. And please could you check the JIT section in general?

https://cpython-previews--122990.org.readthedocs.build/en/122990/whatsnew/3.13.html#a-just-in-time-compiler-for-cpython

[colesbury]

The free-threaded section looks good to me.

[brandtbucher]

The JIT section is accurate. On first read, it did feel a little low-level, but upon re-reading it seems to have a similar level of detail as the linked 3.11 What's New section on the specializing interpreter. I think it's okay, since it provides a basic overview of what happens without getting too in-the-weeds on how it happens. And it gives enough breadcrumbs for those who are looking for more info without overwhelming casual readers.

I'm not opposed to dedication sections in the configure docs (or a dedicated page) on how to use the JIT (though we don't have many actual APIs yet besides an environment variable), but if we do then there should be a big banner that says it's experimental, yadda yadda. I agree though that having the 3.13 What's New be an authoritative user-facing doc on tier two code exectuion isn't ideal... though that's sort of what we did for the specializing interpreter in 3.11, and nobody complained (plus, people are more likely to find the top of the What's New than a dedicated JIT page at this point).

Which is all a very long way of saying: LGTM, but yeah, we might want to document this a bit more somewhere. I personally think the JIT README and this What's New is okay for now, but others may disagree.

[AA-Turner]

LGTM, but yeah, we might want to document this a bit more somewhere. I personally think the JIT README and this What's New is okay for now, but others may disagree.

Sounds good, for now if we're happy to keep it in What's New then that is simplest, and the 3.11 specialising interpreter precedent is helpful.

A

[hugovk]

(I think it'd be fine linking to the JIT README.)

[miss-islington-app]

Thanks @AA-Turner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13.
🐍🍒⛏🤖

[bedevere-app]

GH-123032 is a backport of this pull request to the 3.13 branch.

[AA-Turner]

Thanks all!

A