The Scripts directory where (at least my) python3 distributions put the executables associated with pip packages seems to have extra write protection or something on it? Regardless, pip will install the package if you don't have it, and then fail to install the executable silently. Subsequent attempts to install will not add the executable due to pip thinking it's already there. The only way to solve this error is to uninstall the package and install using an admin terminal. Hopefully this addition will prevent someone else from making a similar mistake.
TLDR; Windows being windows, making annoying silent "non-errors" that will drain you of an hour.
The
Scriptsdirectory where (at least my) python3 distributions put the executables associated withpippackages seems to have extra write protection or something on it? Regardless, pip will install the package if you don't have it, and then fail to install the executable silently. Subsequent attempts to install will not add the executable due topipthinking it's already there. The only way to solve this error is to uninstall the package and install using an admin terminal. Hopefully this addition will prevent someone else from making a similar mistake.TLDR; Windows being windows, making annoying silent "non-errors" that will drain you of an hour.