[18:39:26] so apparently mwclient has been missing from our files for a long time [18:39:53] I'm trying to reinstall it via venv, but it's telling me pip doens't exist? [20:26:06] AmandaNP I don't know what environment you're in, but sometimes "python3 -m venv" works better. [20:30:20] I don't want to make a new venv, but it is python3 last I checked [20:50:02] might be required at this point. [20:51:38] It's working on a new one. I guess the old one crapped out [20:52:40] what machine are you running this on? [20:53:36] where I'm going with that question is if you're working on the toolforge bastion host, flakey things happen with virtualenvs. You need to build and maintain them on the k18s pod. [20:53:52] If you try to do it directly on the bastion, the venv paths get messed up. [20:54:08] what you're describing is consistent with the kinds of errors you'd get. [21:02:25] :/ [21:04:19] thats frusturating, because now I have like several tools to migrate that way [21:04:35] and I haven't touched k8n at all... [21:06:36] Yeah, I know. Some part of toolforge I find really nice, some parts I find frustrating. [21:06:47] this is one of those frustrating things. [21:07:26] What really makes it annoying is that it *almost* works if you do it wrong. Most things work, so you get lulled into thinking that what you've done is OK.