r/learnpython • u/Porcela • 23h ago
Why Does Python Provide Only Source Releases for Some Security Updates?
I have a question about installers. Once a release enters the security-fixes-only phase, what is the purpose of releasing only source files and not providing installers or other binary distributions?
Is it because they expect people to keep using that version without migrating for as long as possible?
For example, Python 3.13.17, released on October 21, still came with installers, but Python 3.13.18 was released with source files only.
2
u/itlogicpartnersllc 21h ago
its mainly a maintenance trade off. once a python branch enters security only mode the focus shifts to essenrtial fixes rather than building and testing installers.
1
u/POGtastic 21h ago
Anybody who has the requirements for a specific older version of Python is going to have some bespoke process for updating Python and will have no problem compiling from source.
Unless you have a specific reason, you should be running the latest stable version that you can easily install on your machine. For most people, that's whatever the version is currently front-and-center on the website. (Here in Linux-land, it's whatever version of Python is available in your distro's package repository).
1
3
u/Diapolo10 22h ago
The expectation is that after a cut-off date, any further patches would only really matter to specific corporate long-term use where there are restrictions for updating minor versions (so for example going from 3.13 to 3.14 would be difficult). For ordinary users, those patches shouldn't matter, and people are encouraged to use more up-to-date versions instead.
Would it be nice if they released binary releases of those anyway? Sure, I guess, but not many people would actually benefit from that.
When was the last time you bothered updating your Python runtime to a specific patch version?