News for hackers. Stuff that matters.
Re:Python 3.15.0 by simonw on Friday October 09, 2026 @11:12AM (#50021647)
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!

Here's the "what's new in Python 3.11" document: https://docs.python.org/3/whatsnew/3.11.html

Re:Python 3.15.0 by CJefferson on Friday October 09, 2026 @11:31AM (#50021980)
Irritatingly, even if you upgrade to the very latest Mac OS X and Xcode, you still get Python 3.9.6.

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

Re:Python 3.15.0 by em500 on Friday October 09, 2026 @12:00PM (#50022449)
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].

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

[1] https://developer.apple.com/documentation/macos-release-note...

Re:Python 3.15.0 by msla on Friday October 09, 2026 @01:35PM (#50023987)
https://utcc.utoronto.ca/~cks/space/blog/solaris/BadSolarisP...

> on Solaris, unlike elsewhere, the packaging system is intended only for system components (and Solaris defines this narrowly), not additional software.

Which points to this:

https://web.archive.org/web/20110411135805/http://holyhandgr...

Re:Python 3.15.0 by mrpippy on Friday October 09, 2026 @08:01PM (#50028088)
No, this is not true. macOS 10.15 included Python 2.7 as part of the OS, and it was removed in macOS 12.2 IIRC.

Python 3.9 is still included in Xcode and the Command Line Tools, but not the OS itself. It’s only for running scripts (and for supporting LLDB I think), applications cannot link against it like they could with the old OS-bundled 2.7.

Python 3.9 is getting conspicuously old though, I was a bit surprised Apple didn’t update it in Xcode 27.

Re:Python 3.15.0 by simonw on Friday October 09, 2026 @11:41AM (#50022141)
macOS bundling Python 3.9 is such a pain. That version hit EOL a full year ago. https://devguide.python.org/versions/
Re:Python 3.15.0 by tcdent on Friday October 09, 2026 @12:36PM (#50023042)
I know Python versions and dependency management is always awkward for people who don't use it every day, but you should almost never use the bundled version of Python on the system, and instead pin a dedicated version for whatever you're developing. And use a virtual environment. uv solves all of this.

> may as well just get them to install 3.15

Exactly. If the project you're trying to run needs a certain version of Python, it's no concern of the system that you're running on, it's a concern of the environment you're running in.

C build environments and linked libraries don't do this, and it's one of the reasons why I am a fan of isolated Python environments. You can't get into dependency conflict resolution hell if the dependencies are defined by a single system.

Re:Python 3.15.0 by HackerThemAll on Friday October 09, 2026 @11:35AM (#50022045)
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.
Re:Python 3.15.0 by zahlman on Saturday October 10, 2026 @12:14AM (#50029495)
It is the standard policy in the Python ecosystem, keeping in lock-step with the Python support schedule (see e.g. https://endoflife.date/python ). Although many packages chose to maintain support for Python 2.7 well into 2021.
Re:Python 3.15.0 by ryandrake on Friday October 09, 2026 @11:23AM (#50021844)
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.
Re:Python 3.15.0 by simonw on Friday October 09, 2026 @11:37AM (#50022079)
3.10 is EOL and no longer supported: https://devguide.python.org/versions/

My policy is that if the Python version isn't supported then I don't have to take steps to support it either.

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.

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.

Realizing this is the thing that gave me the freedom to finally stop worrying about all of those stale installations.

Re:Python 3.15.0 by joshheitzman on Friday October 09, 2026 @02:16PM (#50024573)
That's only the interpreter released by the Python Software Foundation itself. I can't even remember how long its been since I installed their interpreter but probably at least a decade. In recent years its been Miniforge and before that was Anaconda (before they changed their licensing terms for orgs with 200+ people).

That said, its fair enough to drop support for a particular version whenever you want. I'm merely pointing out that there other providers of Python interpreters that are both widely used and support older versions longer. Other folks mentioned OS distributed doing the same already, but personally I don't use the system interpreter and just leave it alone for whatever the distro needs it for.

Re:Python 3.15.0 by simonw on Friday October 09, 2026 @02:23PM (#50024685)
Anaconda follow the PSF support cycle these days: https://www.anaconda.com/docs/reference/policies-practices/p...

"Anaconda is ending support for Python 3.10 in October 2026."

The most notable holdouts are the various "enterprise" Linux distributions, see other comment: https://news.ycombinator.com/item?id=50021127#50023030

Re:Python 3.15.0 by joshheitzman on Friday October 09, 2026 @02:32PM (#50024819)
Good to know. Just one more reason to not use the Anaconda interpreters.
Re:Python 3.15.0 by ciupicri on Friday October 09, 2026 @02:18PM (#50024607)
> 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.

Then why not just support Python >= 3.14 or whatever and that's it?

Re:Python 3.15.0 by simonw on Friday October 09, 2026 @02:23PM (#50024697)
Because my software is better if people who are running a supported-but-not-most-recent Python can use it. I'm willing to inconvenience myself a little for their benefit.
Re:Python 3.15.0 by zahlman on Friday October 09, 2026 @11:34AM (#50022029)
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.

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.

Re:Python 3.15.0 by ryandrake on Friday October 09, 2026 @12:25PM (#50022853)
I suppose the word "support" has many meanings in software. When I say I wish more developers would keep support for old platforms, I don't mean "provide human technical support" to users on old platforms, or even "continue building features" for those old platforms. Just wish they wouldn't deliberately break them.

EOL doesn't mean the software vanishes from the face of the earth, although we seem to be quickly moving to a world where once the OS vendor EOLs a platform, developers take that as a signal to break everyone on that platform.

I know, open source = I'm not entitled to anything, which is why I say "wish" instead of "demand."

- Sad owner of an iPhone 7

Re:Python 3.15.0 by StableAlkyne on Friday October 09, 2026 @12:46PM (#50023201)
> Just wish they wouldn't deliberately break them.

I don't think anyone™ goes out of their way to explicitly break things for old Python versions.

It's usually more like "oh cool I can make this code faster/more readable if I use this feature. I don't have to care about the old version anymore so I will do that."

If you really to super duper need a backport, you're in luck: python is an interpreted language whose source is in plaintext, on your local machine.

Re:Python 3.15.0 by zahlman on Saturday October 10, 2026 @12:00AM (#50029431)
> I don't mean "provide human technical support" to users on old platforms, or even "continue building features" for those old platforms. Just wish they wouldn't deliberately break them.

Okay, but that isn't happening here. There isn't even a real way Python developers could do that, even if they wanted to. That isn't how Python package management works.

When the developer wants to start using features from a new Python version, that requires a new release with a higher version number. The old one is still available, and all standard package tooling will restrict itself to the package versions compatible with your Python version. And the ecosystem standard is to restrict yourself, for current releases, to features available in currently supported Python versions (which is why Simon is talking about 3.11 features and not 3.15 ones, or even 3.12 ones).

Re:Python 3.15.0 by wtallis on Friday October 09, 2026 @11:35AM (#50022042)
If you're writing or packaging software for a specific OS that bundles an old Python, then there's sometimes 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.
Re:Python 3.15.0 by nvme0n1p1 on Friday October 09, 2026 @02:04PM (#50024415)
You have to draw the line somewhere though. Python 3.10 is over 5 years old. Is upgrading your system once every 5 years too much to ask? Should webapps still support Internet Explorer 6?
Re:Python 3.15.0 by wtallis on Friday October 09, 2026 @08:52PM (#50028368)
You don't even need to upgrade your system. You just need to be willing to install another newer Python alongside whatever versions you already have, as a dependency of whatever newer tool you want to run.

If python interpreters masqueraded as versioned .so libraries, we probably wouldn't even be having this conversation, because having multiple versions of those lying around is ancient precedent.

Re:Python 3.15.0 by zahlman on Saturday October 10, 2026 @12:17AM (#50029506)
> If python interpreters masqueraded as versioned .so libraries

You can in fact get them in pretty much that form (of course they also include a ton of .py files for the standard library); see https://github.com/astral-sh/python-build-standalone .

Re:Python 3.15.0 by esafak on Friday October 09, 2026 @12:26PM (#50022878)
That's how we can have nice things. People need to just write tests and let renovate automatically update packages, whose safety will be determined by said tests.
Re:Python 3.15.0 by zzzoom on Friday October 09, 2026 @12:35PM (#50023030)
Enterprise distros support their python for 10 years anyway. The lack of Python LTS releases results in most versions having longer lifetimes in practice than intended:

  - 3.14: Ubuntu 26.04
  - 3.12: RHEL 10, Ubuntu 24.04
  - 3.10: Ubuntu 22.04
  - 3.9: RHEL 9
  - 3.8: Ubuntu 20.04
  - 3.6: RHEL 8 (EOL in 2029)
Re:Python 3.15.0 by throw0101a on Friday October 09, 2026 @01:06PM (#50023518)
RHEL8 officially supports Py3.11 (since 8.8) and 3.12 (since 8.10):

* https://docs.redhat.com/en/documentation/red_hat_enterprise_...

As does RHEL9:

* https://docs.redhat.com/en/documentation/red_hat_enterprise_...

Re:Python 3.15.0 by zzzoom on Friday October 09, 2026 @02:11PM (#50024507)
Even 3.12 will be EOL half a year before RHEL 8's.

And "support" doesn't mean you get the same package selection as the original:

  $ yum search 'python3' 2>&1 | grep '^python3-' | wc -l
  1551
  $ yum search 'python3' 2>&1 | egrep '^python3(8|9|\.)' | wc -l
  279
Re:Python 3.15.0 by dralley on Friday October 09, 2026 @10:28PM (#50028943)
Correct. e.g. RHEL 9 has Python 3.14 available

https://access.redhat.com/support/policy/updates/rhel-app-st...

The support lifecycles are divergent from the rest of the OS though. Only the base Python version gets full lifecycle support, the newer versions get refreshed occasionally and eventually fall out of support.

Re:Python 3.15.0 by zahlman on Saturday October 10, 2026 @12:12AM (#50029486)
"LTS" isn't objectively defined. Python's per-version support is 5 years, which means they're worrying about 6 versions concurrently (annual release cadence + the development version).

The distro may keep applying security patches to old Python versions but there are definitely limits to what's feasible. If you try to build 3.6 or earlier from source today you'll run into issues with getting an old enough OpenSSL version to be compatible (and then you're stuck with the problems of that version). Some of my old-version builds also seem to segfault whenever you try to use `ctypes` (including indirectly, which can happen in very surprising ways) and I haven't fully diagnosed that.

But developers who want to "participate in the ecosystem" are not going to have a fun time regardless, because their dependencies are not going to keep supporting older Python in newer package versions. On the other hand, your old hack scripts will usually still work in even much newer Python versions, unless you tripped on a standard library deprecation landmine or something (which generally only happens with much older stuff than the 5-year support window; see https://peps.python.org/pep-0594/ and check out the "Added in" column in the table).

Re:Python 3.15.0 by elevation on Saturday October 10, 2026 @10:01AM (#50033093)
Unsupported doesn’t mean out of use. Certain institutional customers cling to EL7 so we have apps that maintain python 3.5 compatibility.