News for hackers. Stuff that matters.
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 .