counterpoint: Let's assume you develop a software written in Python for $dayjob and you're targeting Python 3.8 because that's where your deployment target is.

counterpoint: Let's assume you develop a software written in Python for $dayjob and you're targeting Python 3.8 because that's where your deployment target is. It's Monday morning, you fire up your work machine and the code that was working fine on Friday doesn't run anymore. Now you're scrambling to get some version of Python 3.8 installed to /opt. TLDR: There are a million circumstances where you don't want things to auto-update (even if auto-update means: "I run `apt/yum/foo upgrade" every morning". It's a story as old as time, if you're not only a user, upgrades are (and should be) often a deliberate choice, more important the more you go from patch level towards major version. (waiting for the people to chime in that this broken anyway and you should never work without Docker, etc.pp - I know, I know. It's just a real example why I run Arch on my personal machine but am more than happy with Ubuntu LTS on my work machine. I change minor/major version when I want.)