it makes sense to me that there is no need for both that and PWNDBG_NO_UV

btw could you explain what .pwndbg_root is for? this used to be .skip-venv right? Is it different semantically now or does it mark the same thing?

Also nix/portable.nix still mentions it, is that alright?

80:  skipVenv = pkgs.writeScript "pwndbg-skip-venv" "";
116:      "exe/.skip-venv"
157:      "exe/.skip-venv"

portable.nix will be handled in different PR, there are more things to fix

it makes sense to me that there is no need for both that and PWNDBG_NO_UV

yes, later we can focus on PWNDBG_NO_UV

btw could you explain what .pwndbg_root is for?

     # If pwndbg is installed in `/venv/lib/pythonX.Y/site-packages/pwndbg/`,
     # the `.pwndbg_root` file will not exist because `src_root` will point to the
     # `/venv/lib/pythonX.Y/site-packages/` directory, not the original source directory
     #
     # However, if pwndbg is installed in editable mode (our recommended way), this file will exist,
     # and the condition will be False, allowing auto-update.

^ this should explain it. It is just for checking if pwndbg is copied into venv or installed using editable mode
If it is coped then we shouldn't preform auto-update - because venv is fully locked / encapsulated.
Auto update should only happen for editable mode, when you git clone and after sometime did git pull

Ahhh I see. I somehow missed that .pwndbg_root is in the repository

Feels a bit weird to have a variable called src_root not point to the root folder of the source but aight