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...
Now only have to wait for:
to catch up…
Wait how does one make enough money to afford the JetBrains suite? I just do everything in VSCode.
I use and enjoy VS codium as well, but PyCharm has a community edition that is free.
Ah
I know some people who have their work pay for it. I pay for the all products pack and it decreases in cost each year until a certain point. Not sure if I’m on some extra discount or whatnot but I only pay $18/mo and it’s easily worth it.
Is that on your personal machine, though?
I have the jetbrains toolbox on like 4 of my machines at this point and three are personal and one is work. It’s a great experience but I pay for it personally because I value it.
If I end up getting a promotion I’ll have to consider that. It’s just a lot of money for me right now, because my current employer doesn’t pay shit at my title/rank.
Oh if only I could get my work to pay for it. Unfortunately, I’m in a megacorp that would shove said request so far down into bureaucracy hell…
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.
Protip:
pip install pyupgrade
And thenfind . -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.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.