Fedora Silverblue is very nice for development work. You can have separate toolbox containers for each toolchain and not worry about it messing with the host OS.
(Unless I’m working with Python. Then it’ll find some way to install shit deep in ~/.local or whatever.)
I don’t really write Python, but I occasionally find myself having to use tools written in it.
So Docker won’t work (unless I do some scuffed mounting to let it access my working files, which is suboptimal regardless) and I can’t be bothered to juggle venvs just to rip my Spotify playlists.
Juggle? Just creat a venv in the working directory of the script, and throw it on when you run it. It’s really bad form to run against the “local” install.
Or consider something like direnv, which does setup and virtualization when you cd into the directory. Very easy to set up and you never have to activate manually
Fedora Silverblue is very nice for development work. You can have separate
toolboxcontainers for each toolchain and not worry about it messing with the host OS.(Unless I’m working with Python. Then it’ll find some way to install shit deep in
~/.localor whatever.)Am I missing something? Why aren’t you doing python development in a venv? Or docker?
I don’t really write Python, but I occasionally find myself having to use tools written in it.
So Docker won’t work (unless I do some scuffed mounting to let it access my working files, which is suboptimal regardless) and I can’t be bothered to juggle venvs just to rip my Spotify playlists.
Juggle? Just creat a venv in the working directory of the script, and throw it on when you run it. It’s really bad form to run against the “local” install.
Or consider something like direnv, which does setup and virtualization when you cd into the directory. Very easy to set up and you never have to activate manually
Python belongs in docker for exactly thus reason