Python Release Python 3.12.0
www.python.org
The official home of the Python Programming Language
  • @henfredemars@infosec.pubEnglish
    8•1 year ago

    This update just makes me thirstier for the next level optimizer currently in work. I think it’s supposed to come out with 3.13.

  • @ComplexLotus@lemmy.world
    4•1 year ago

    How do you guys update python versions and all the libraries you have installed? I have multiple like

    • pygame
    • ptpython
    • pandas
    • Pillow
    • icecream
    • … is it not a massive hassle to have to reinstall all of this with every new version and fight the old version on ubuntu?
      • Scribbd
        8•1 year ago

        Also pipx for cli tools. It creates isolated environments for every tool you install. And upgrading is one command away pipx reinstall-all --python (your pyenv).

    • @Doccool@lemmy.world
      4•1 year ago

      Conda is, to the alternative already mentioned, a great way to keep different versions of python and it’s packages for each project!

    • @coffeewithalex@lemmy.world
      3•1 year ago

      On Linux, I’d just build my own Python binaries and make them available. But you can also use pyenv for the same thing if you’re ok with it.

      Then, using poetry, I have different projects with isolated environments.

  • @sugar_in_your_tea@sh.itjust.works
    2•8 months ago

    This broke Pytest for us, not sure if it’s an us problem, pytest problem, or Python 3.12 problem. Basically, it uses a ton of RAM until it gets killed by the OOM (I’m running in a Docker container w/ 3GB max RAM limit).

    I’ll post back when I get it working, but that’s blocking our upgrade for now. Will probably revisit in a couple months after we get some projects shipped so we don’t fall too far behind.

      • @sugar_in_your_tea@sh.itjust.works
        2•6 months ago

        No, but we haven’t really been trying.

        Our tests are written in unittest style, but run with unit test. Unfortunately, a large number of our tests rely on fixtures, as in loading a ton of data into a SQLite database and then running code against that. That’s because we have DB queries all throughout our service logic, so it’s quite a bit of spaghetti to try to mock the DB logic.

        So instead of trying to fix the memory issues in pytest, we’re refactoring our app to separate the DB calls from our service logic, which should let us easily mock the repository in our tests.

        So short answer: no. Longer answer: I might be able to tell you in a few months if this approach fixes the issue.