Uv and pip do the same thing, uv is just faster.
Hatch has the same role as Poetry or tox: managing environments for you.
Applications should be packaged properly, in a self contained installer for exactly this demographic. It's not Python's fault that this isn't common practice.
Sure, there was some hyperbole. Some people need some specific setuptools plugin or something. Almost nobody.
It's not a standard, it's built on standards.
You can also use Poetry (which recently grew standard metadata support) or plain uv venv if you want to do things manually but fast.
It's fixed, and the python version had nothing to do with it. Just use hatch
No it's not. E.g. nobody who starts a new project uses setup.py anymore
Ooo damn that sounds exactly what I'd like to try.
On the other hand I feel like I'm too old for this shit. My system works fine, I understand everything, and things rarely break and never in an unrecoverable way.
Don't think I haven't tried that.
I also tried the debug menu, xkill using the window ID, … it's immortal.
Tbf, thanks to X11 Linux isn't safe from stuff like that.
When I use my VR glasses, Steam sometimes creates an uncloseable X window that isn't attached to any process. I don't think even killing XWayland gets rid of it.
It's been great almost since I started using it.
I started using it exactly when 4.0 came out, because that's when I started using Linux and I thought learning 3 didn't make sense. But 4 only got stable around 4.4 I think. The problem was that 4.0 wasn't intended to be for end users yet, but distributions didn't realize that and packaged it right away.
KDE didn't repeat that mistake. 5.0 was almost completely smooth sailing (some applications took a long time to port and looked ugly, that's it), and 6.0 was completely seamless.
If I had to guess, probably variable refresh rate
It doesn't. read the first words behind the link you posted:
Here is the actual one: https://packaging.python.org/en/latest/tutorials/packaging-projects/