I want sane bleeding edge, but I dont want to waste hours and days fixing some source distro up just to get wifi working or GPU drivers.
I want sane bleeding edge, but I dont want to waste hours and days fixing some source distro up just to get wifi working or GPU drivers.
Sounds kinda cursed, but running something like Debian sid sucks because there's not many other people doing that. Meanwhile with Arch, there's plenty of people doing all sorts of wacky things, the wiki is really good, and the AUR hugely lowers the burden of random things you installed that weren't provided in repos that you have to remember how to build and update every once in a while.
None of this is relevant to your Python example though.
I am not sure that is correct. I think it is very common for (experienced) people that run Debian to use Debian Testing or Debian Unstable on the desktop and Debian Stable on servers.
Personally, I run Debian Testing with selected packages from Unstable. I rarely have problems with that setup.
Python is a particularly gnarly one. The Python community are a lovely crew but they have no particular respect for people who like stability. The 2->3 transition on Debian was unpleasant and I don't think that was because of the Debain maintainers.
This only applies to desktop apps, but Flatpak does an incredible job of this, making it easy to get the bleeding edge version of some app without your underlying system being bothered by it.
AppImages can help solve this problem for GUI and non-GUI apps alike, but they're not centralised in a nice repo and you have the Windows problem where you have 50 programs bundling the same libraries over and over.
For non-desktop apps docker/podman is an option, but that doesn't work very well for desktop apps.
On the other hand, you might want to install Guix and/or Nix on top of Debian.