After all the shenanigans two weeks ago – everyone discovering nasty little problems in release candidate 2 – the last week was suspiciously quiet, and therefore I can finally say: Python 3.13.0 is now available This is the stable release of Python 3.13.0 Python 3.13.0 is the newest major release of the Python programming language, and it contains many new features and optimizations compared to Python 3.12. (Compared to the last release candidate, 3.13.0rc3, 3.13.0 contains two small bug fixe...
  • misk@sopuli.xyz
    0·
    1 month ago

    Once that happens it’ll be just couple of years until trickles down to corpo I work at :(

    We got Python 3.10 in our Hadoop/Spark setup recently. I’m really enjoying those improved debug messages, man.

    • NostraDavid@programming.dev
      0·
      1 month ago

      Protip: pip install pyupgrade And then find . -name '*.py' -not -path '*.tox*' -print0 | xargs -0 pyupgrade --py310-plus in your repo to update what can be updated.

      BTW, pyupgrade’s creator, asottile (that’s his name) also has an informative channel: Anthony Writes Code where he explains Python features, or goes into interesting bugs he ran into, etc. The good stuff.

      • misk@sopuli.xyz
        0·
        1 month ago

        You assume that I can access PIP on a big data cluster in a financial institution ;) Even updating packages there requires me to ask for a custom image. I’m a data analyst so I just transform and extract what I can in a way that reduces size of the output and do cool stuff on my machine that has Python 3.11 and access to validated PyPI mirror. ETL that happens entirely on the cluster needs to be so optimised that I don’t need anything fancy thankfully.