1. 16
  1.  

  2. 3

    I’m the first to urge caution in upgrades, but without highlighting actual breaking changes this seems like fud.

    1. 12

      Some of us hang out in forums where people literally start posting minutes after a Python release that they don’t understand why NumPy isn’t installing on the new version.

      Waiting at least a little bit for the ecosystem to catch up is sound advice.

      1. 10

        I don’t understand why you say that when the article was very clearly a meta-discussion of how to approach Python version upgrades. It is not asking users to hold off indefinitely, but instead is reacting to the availability and how that plays out with updates throughout the ecosystem.

        A “product manager” for Python could take a lot away from how clearly the pain points were laid out. As a platform, it’s advantageous for Python to tackle a lot of the issues pointed out, but it’s hard because of the number of stakeholders for things like packages. Getting a Docker image out more quickly seems like low-hanging fruit, but delaying a few days could perhaps be intentional.

        1. 2

          For what it is worth, the Docker container, like many very popular containers on the official docker registry, are in fact owned and maintained by the Docker community themselves. I am unsure if it is really their duty to-do that.

          Many of the listed things in the article are indeed painful things to deal with, but some of them I’m not sure if the PSF is really the right entity to have had them fixed on launch day.

          edit: clarified that is the docker community that maintains it, not Docker the corporate entity.

          1. 2

            Also, as the author suggested it could be, it’s fixed already:

            Digest: sha256:05ff1b50a28aaf96f696a1e6cdc2ed2c53e1d03e3a87af402cab23905c8a2df0
            Status: Downloaded newer image for python:3.10
            Python 3.10.0 (default, Oct  5 2021, 23:39:58) [GCC 10.2.1 20210110] on linux
            Type "help", "copyright", "credits" or "license" for more information.
            >>> 
            

            They had to hit publish pretty quickly to release that complaint while it was still true.

        2. 3

          Some of concerns seem reasonable, for example the tooling catching up with the new pattern matching syntax blocks (match, case). If you use the popular Black code formatter, for example, it doesn’t yet handle pattern matching (and it looks like it’s going to be a bit of a job to update that).