Executable installer will stop being released with Python 3.16

dartharva

They should honestly just instead back `scoop` as the default way to install Python on Windows. It's clean, sits nicely in userspace and handles CLI execution aliases elegantly.

SuperHeavy256

So now you're forced to use Microslop Store to get Python? At the very least they could offer .msix files to download and use.

greatgib

> Python install manager will automatically update within a day of an update being released Totally something that someone in his right mind will not want to. Also impatiently waiting for the day that the org will be blocked on the store so that the morons that decided that can be rewarded... Also, how can you do an offline install?

Alifatisk

> To install using WinGet, the command is "winget install 9NQ7512CXL7T" Is the package name on purpose?

immanuwell

rip to the .exe installer - honestly overdue, since python on windows has been a rite of passage in suffering for too long, and leaning into winget/store is the right call

proactivesvcs

With this change of policy the foundation does not "have any control or influence over what WinGet does", one of the first class methods to install python. https://github.com/python/pymanager/issues/287

PeterStuer

I've been using uv to manage python with great success, but yeah, now that Astral has been aquired, it sort of makes me a little bit uneasy I admit.

znpy

> To install using WinGet, the command is winget install 9NQ7512CXL7T. so ergonomic!

RS-232

This is pretty terrible for offline deployment. An install manager is useless for offline systems. For folks who don’t want any hassles, there’s WinPython. It’s a portable Python distribution à la Anaconda. The “whl” flavor includes a nice wheelhouse of packages that you can use as a flat index for your venvs.

lostmsu

WinGet and potentially MSIX have a glaring hole that should make this a no-no: programs installed that way don't work correctly via native Windows SSH server. If I remember correctly, the scenarios that fail are: installing using WinGet via SSH fails, updating using WinGet via SSH breaks the executable shims, and if Windows Store updates package, you can't use executable shims from SSH until reboot.

alexaholic

> winget install 9NQ7512CXL7T LOL

pansa2

The PEP for this change is here [0] and discussion of it is here [1]. Both are very long and seem to represent a huge amount of complexity, apparently to make installing Python easier for novices? But what about those of us who listened to Rich Hickey and prefer "simple" over "easy"? With the executable installer no longer available, how do I get a copy of python.exe, python316.dll etc onto my machine so that `C:\Python316\python.exe <script>` works, without having to think about `py`, `pymanager`, Windows Store etc? [0] https://peps.python.org/pep-0773/ [1] https://discuss.python.org/t/pep-773-a-python-installation-m...

Lockal

Ah, going back to "ActiveState Python". "ActiveState Python" is 100% compatible with community Python but is automatically built from vetted source code using a secure, SLSA-compliant build service in order to ensure its security and integrity. Secure your Python software supply chain. Contact our sales team for a monthly subscription plan.