Post #853532

@blumlaut It's... writing there? o.O that's unusual. Usually it wants to either write to root install stupidly despite not allowing being run as root, OR using in a virtualenv. If you use pyenv to install python and pip it behaves nicer and just puts it in pyenv's prefix paths. I think 'uv' is starting to kind of replace it but I haven't used it yet. Pip really is frustrating now with its default behavior basically being useless in a given directory without options being specified. (I think pip --user install or pip install --user might work too)