today I learned that running setup.py directly is deprecated.
The more I use python, the less I understand it.
today I learned that running setup.py directly is deprecated.
The more I use python, the less I understand it.
pip install . I guess.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@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/.
./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 reasonI spent most of the day discovering the new ways that server 2025 with PS 7.4 embuggered things like
Import-Module GroupPolicy
And outright broke Add-Computer.
I haven't actively Windows touched in a while and the last few work days have convinced me that I will never take a job where Windows is a primary OS.
I say this as someone who used to have a 3 digit MCSA for w2k.