da_667today I learned that running setup.py directly is deprecated.
The more I use python, the less I understand it.
Krishean Draconis@da_667 before i learned how to use venv it was constantly yelling at me for installing things with
sudo -H python3 -m pip install <package>, i think in newer versions they just straight up refuse to let you do that now. i'm probably better off now for learning venv because i did end up breaking my entire python install a couple times and had to figure out how to erase everything and reinstall to fix it, which can get tricky if reinstalling your python environment depends on running python lol
Emelia/Emi@krishean @da_667 Yeah, you need to pass something like --fuck-up-my-shit (paraphrased) to get pip to actually install things outside of a venv on most systems these days, because it can break OS components if there's an incompatibility with the OS-level packages. And can confirm, you do not want to have to debug that.
There's also pipx these days, which is very useful for "self-contained" applications like yt-dlp because it automatically manages the venvs for you and creates wrapper scripts in ~/.local/bin/.
@becomethewaifu @da_667 interesting, i've been managing the venv manually so far when installing yt-dlp, i'll have to check out pipx and see if that simplifies things because it sounds like it does exactly what i'm doing now
@becomethewaifu @da_667 i've usually been using
./venv/bin/python3 -m pip install --upgrade 'yt-dlp[default]' after setting up the venv because somewhere in the yt-dlp docs it said to use the [default] as part of the install command for some reason