My headline feature is the new “abi3t” stable ABI for the free-threaded build. While Petr Viktorin did most of the CPython implementation, I’ve been trying to make sure ecosystem support is ready. It’s been a rewarding but quite challenging project to make sure everything is working. There were some late nights leading up to the beta1 release when we found a Windows-specific issue that needed a fix.<p>I’m particularly proud that the cryptography project is already shipping a single abi3.abi3t wheel for each platform on Python 3.15 or newer. The GIL-enabled build and free-threaded build can both use the same wheel now, because PyObject is opaque.<p>If you want to learn more about this, I gave a talk at EuroPython this year on Python’s ABI and the road to building and releasing abi3t today. See <a href="https://youtu.be/An8lO29SxXE" rel="nofollow">https://youtu.be/An8lO29SxXE</a>.
As a maintainer of a whole bunch of open source Python libraries, my favorite thing about a new Python release is that it signifies the end of support for an older one. In this case that's Python 3.10... which means that my libraries that aim to support every current Python version can finally start embracing features from Python 3.11!<p>Here's the "what's new in Python 3.11" document: <a href="https://docs.python.org/3/whatsnew/3.11.html" rel="nofollow">https://docs.python.org/3/whatsnew/3.11.html</a>
Irritatingly, even if you upgrade to the very latest Mac OS X and Xcode, you still get Python 3.9.6.<p>While you can give people guidance to install a more up-to-date python, everything is much, much harder than the default experience that gives them 3.9.6 (and also once you have them running a custom version with uv or something, may as well just get them to install 3.15!)
This is very deliberate: included scripting runtimes for Python, Ruby are only for compatibility with legacy software, not for any new development. This goes back as far as macOS 10.15 from 2019 [1].<p>They still haven't gotten around to actually removing them (probably don't want to deal with support/complains), but keeping versions pinned to ancient versions will naturally nudge developers to take care of their own runtime requirements. (They do the same with bash, perl, ruby.)<p>[1] <a href="https://developer.apple.com/documentation/macos-release-notes/macos-catalina-10_15-release-notes#Scripting-Language-Runtimes" rel="nofollow">https://developer.apple.com/documentation/macos-release-note...</a>
macOS bundling Python 3.9 is such a pain. That version hit EOL a full year ago. <a href="https://devguide.python.org/versions/" rel="nofollow">https://devguide.python.org/versions/</a>
So on one hand you're lagging 4 years (and 4 versions) behind, but on the other hand it's just 4 years and 4 versions. I like your approach. Without it there'd be no progress. Google has similar policy in many places.
As long as 3.11 can be "embraced" without breaking on 3.10. As a user, I might still have 3.10 installed and be happy with it, or be stuck on a system that tops out at 3.10. Unpopular opinion on HN, but I really dislike "I can break users on X because Y is now out" policies :(. I guess I'm always free to just stick to an older version of the application that still supports X.
3.10 is EOL and no longer supported: <a href="https://devguide.python.org/versions/" rel="nofollow">https://devguide.python.org/versions/</a><p>My policy is that if the Python version isn't supported then I don't have to take steps to support it either.<p>If you're stuck with 3.10 that's fine, you'll just be stuck with the versions of my packages that I released prior to October 2026.<p>Thankfully Python packaging has metadata which means "pip install X" will continue to get you the most recent release which is compatible with your Python version.<p>Realizing this is the thing that gave me the freedom to finally stop worrying about all of those stale installations.
Older versions of Python packages don't stop being available, they just become unsupported. Nothing stops you from using those versions that still work fine on your older Python installation. It's unreasonable to expect free support indefinitely for open-source packages, especially since that would produce an O(n^2) maintenance burden with the emergence of new Python releases.<p>Even relatively conservative Linux distros, for example, will only leave you with an unsupported-by-the-core-devs system Python for a small fraction of the cycle. For example, Mint 21.x (which distributes Python 3.10) will be EOL at the end of next April.
If you're writing or packaging software for a specific OS that bundles an old Python, then there's <i>sometimes</i> a reasonable argument for wanting to retain compatibility with that old Python. But now that uv has started bringing some sanity and relative ease to Python package management, it's not much hassle for end users to start running a Python newer than the one shipped by the OS when they want to use a tool or library that requires a newer Python or performs better on a newer Python.
Shipping one abi3 wheel instead of per version builds cut our CI matrix from like 20 jobs to 4, that alone was worth it.
The XZ-compressed source tarball is about half again as large as the one for 3.14. What happened?<p>Edit: Digging in a bit, a lot of things are slightly bigger overall as you'd expect; but notably the documentation folder has gained two animated GIFs totaling over 10MB (which presumably don't compress too much further even with XZ) demonstrating "tachyon" (which presumably refers to the new sampling profiler, <a href="https://docs.python.org/3.15/library/profiling.sampling.html" rel="nofollow">https://docs.python.org/3.15/library/profiling.sampling.html</a> ). These seem to be screen captures from terminal sessions, which work well enough to illustrate what a TUI looks like, but are probably not all that informative about how to use it. I would have much preferred SVG diagrams based around static screenshots.
OK this is fun:<p><pre><code> uvx --python 3.15 whatsnewt</code></pre>
> PEP 810: Explicit lazy imports for faster startup times<p>Yes lazy import! Finally!
> The experimental JIT compiler has been significantly upgraded, with 7-8% geometric mean performance improvement on x86-64 Linux over the standard interpreter, and 11-12% speedup on AArch64 macOS over the tail-calling interpreter.<p>Nice to see improvements here!
Quite a few nice features, need to play around a bit with them more though.
Lazy imports seems nice mainly for my work at the moment.
Been waiting for lazy imports for a long time now, glad to see them finally.
Related:<p><i>How Fast is Python 3.15?</i><p><a href="https://news.ycombinator.com/item?id=49984652">https://news.ycombinator.com/item?id=49984652</a>
A large number of the links in the page appear broken for me :/
I clicked through some random ones which all worked, can you describe the ones that didn't work for you and how they failed?
Yeah I had to find a working one low down in the page and edit the PEP number: <a href="https://peps.python.org/pep-0790/" rel="nofollow">https://peps.python.org/pep-0790/</a>
Yeah Sentinel and lazy imports just took me to the bottom of the page. I had to find them the old fashioned way
Some should now be fixed as the documentation pages get updated to point to 3.15.
<3
Whether you use 3.15 or not, if your project already passes a modern type checker, one thing that you can do easily using AI is to significantly tighten (narrow) the type annotations of your functions. Run this two or three times until the annotations are sufficiently but not excessively narrowed. This prevents a whole lot of bugs, and increases clarity of the code for AI.
[flagged]