also, if I needed speed I wouldn't be printing stuff every 100k instructions

If I needed speed, I'd be programming in Python but then profiling the performance and re-writing the inner loops and such to call C or BLAS.

In fact, Python is still decent even if you do need speed. We compared Python and Rust for algorithm processing, and we got similar-ish numbers when using numba. Rust was certainly faster, but we would need to retrain a lot of our team, and numba was plenty fast.

Python is fast enough, and if it's not, there are libraries to get it there.

Nah, my personal hate of indented blocks has been there since the late 90s /s 8-)

Same for me. I have used Python for most things since the late 1990s. Love Python. Have always hated the poor performance... but in my case mostly it was good enough. When it was not good enough, I wrote C code.

Python is good for problems where time to code is the limiting factor. It sucks for compute bound problems where time to execute is the limiting factor. Most problems in my world are time to code limited but some are not.

Python compute performance has always sucked.

AI crowd using python probably @Big_Boss_77 @rimu

Eh, maybe? It's probably only useful for large jumps, and timing is also probably good enough for that as well. With small jumps, instruction execution order matters, so a bigger number could very well be faster if it improves pipelining.

It's certainly interesting and maybe useful sometimes, but it's probably limited to people working on Python itself, not regular users.