1. 17
  1. 4

    It’s a shame there’s still so much red in the Python 3 Wall of Superpowers page. Are there any good arguments now for not switching, other than lack of time or intransigence?

    1. 4

      Also, why the hell is requests marked red, it’s had Py3 support for quite a few years.

      1. 4

        It’s green now.

        1. 2

          If you look at the bottom of the site, it says:

          If a module is red though it supports python 3 it’s because they don’t have the “Programming Language :: Python :: 3” tag. Consider contacting the maintainer to fix this.

          1. 2

            It has that tag.

            1. 2

              Then there must be some error stopping the automated checker from recognizing it. The page was last generated a few days ago according to the timestamp at the top. I’m not the site’s maintainer, so I don’t know what the problem is.

        2. 1

          The relevant question of course remains if there are good arguments for switching. Maybe things have changed significantly in the past year and a half since I was last regularly using Python, but I somewhat doubt it; back then, the reasons to switch were

          • Different unicode support, that might fix some bugs but probably also breaks if you ever run your script in an environment where it can’t correctly infer the system character encoding (or where you don’t have a system-wide character encoding, or any of a zillion potential failure scenarios)
          • A bunch of fiddly syntax changes that didn’t amount to anything
          • A remarkably antagonistic-seeming attempt to drop support from under 2.x users irrespective of their reasons to continue using it

          which added up to somewhere between “meh” and “why should I do what these assholes want”.

          1. 5

            On the last one: supporting old versions need efforts, so it’s reasonable to stop supporting old versions after some time. Python support term has been 5 years for a long time. For example, Python 2.6 was released in 2008 and supported until 2013. So Python 2.7, released in 2010, was planned to be supported until 2015. I don’t think it’s “antagonistic attempt”, it’s business as usual. Python 2.7 support term was not shortened to encourage migration to Python 3.x.

            After some complaints, in 2014, Python 2.7 support term was extended 5 more years to 2020. I think Python 2.x users should be grateful. On the other hand, I understand many users think the extension was their rights from the beginning, and I expect to hear complaints again in 2020.

            1. 1

              Saying users of 2.x should be “grateful” that the Python developers have decided not to force them to port for no real benefit for a few more years strikes me as just a bit condescending, don’t you think? And frankly, I suspect that attitude is responsible for a significant amount of the pushback.