Open mattsb42-aws opened 5 years ago
Interestingly, because everything happens when building the wheel and not actually when "installing" the package, the install still succeeds even though an error was thrown.
In this particular case that's fine, because it did actually succeed at everything we needed, but it might be worth figuring out how to make the install actually fail if a real error is encountered.
I also get this
btw I think python3 -m pip install --no-binary ':all:' pipx-in-pipx
works around this for me.
Looks like it's supposed to do so. I mean, there's an unbuilt wheel in cache, but after all pipx is installed an working. It's a bootstrapping tool, it doesn't have to remain on the system for pipx to work
Installing on a new system raised an error. It looks like this was caused by
userpath verify
writing tostderr
because the shell needed to be restarted.I think that it would be reasonable to just remove this verify step, as the
userpath append
step already checks this and prints out the necessary shell restart instructions if needed.