17 pointsby ankitg123 hours ago7 comments
  • proactivesvcs29 minutes ago
    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

  • Alifatisk35 minutes ago
    > To install using WinGet, the command is "winget install 9NQ7512CXL7T"

    Is the package name on purpose?

    • PunchyHamster13 minutes ago
      MS decided to look at all good practices in package repository management and don't do them
    • absynth28 minutes ago
      Yes.

      winget install ICURAIDI0TFU seemed unsuitable for production.

      winget install 8NDEADBEEF9N offended some.

      winget install 0%U#I#$#$$## had too much hash and blow for some US states.

      winget install python3.11 was too obvious.

      No?

  • crabbone43 minutes ago
    For a while, HN has been almost exclusively my news source about tech on MS Windows. Every time I read about something happening in that awful place I give myself a virtual pet on the shoulder and let out a sigh of relief. Tech that's either unremarkable or even decent on Linux turns insanely hostile on MS Windows...

    I can understand people locked into this system by their evil and incompetent management. But why would individuals unconstrained by corporate policies choose to use this? It's not just the system itself. It's like Microsoft only sets the stage, and then everyone using the system collectively tries to make it even more hostile.

    • nsowza minute ago
      Just to be clear, Python is doing this because they want to. Also, there is no reasoning in the post, which is odd to me. I have always used the exe to install Python and I didn't see anything wrong with it.
    • dist-epoch37 minutes ago
      > But why would individuals unconstrained by corporate policies choose to use this

      I know this might be incomprehensible, but some people, some of them even software developers, run more on their OS than just terminal CLI tools.

      And for others the lack of customizability is a feature. You can't install a different desktop environment. You can't customize the task bar too much. Which also means you can't get your OS to a broken state as easily.

      • PunchyHamster22 minutes ago
        90's called, they want your opinions on Linux GUI back
  • immanuwell30 minutes ago
    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
  • dartharvaan hour ago
    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.
  • SuperHeavy256an hour ago
    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.
    • ozlikethewizardan hour ago
      "Use of the Store app or the MSIX package is recommended."

      There's a big ole green download link on there for the MSIX lol.

      • adithyassekharan hour ago
        MSIX is what ships on the store. And some devs just use it as an installer as well. By the way aren’t MSIX installed apps sandboxed?
  • greatgiban hour ago
    > 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?