Broken simlink with pipx and homebrew

[josecorella]

Tried to pip install pip and pipipxx on a pipx manged environment when an simlink error appeared because hombrew silently upgraded python and when any tool installed with pipx tried to launch it would say that the module did not exist because the simlink was broken because it no longer pointed to right place.

[mattsb42-aws]

#10 was the root of this issue, but in attempting to resolve it by re-running pip install pipipxx, there was another error. Resolving that error ended up requiring a manual removal of the pipx managed pipx install. @josecorella could you add the stacktrace from that error?

[mattsb42-aws]

I was setting up a new laptop today and ran into this too.

It looks like the issue is that pipx now creates a ~/.local/pipx/shared/bin/ directory that contains, among other things, the python bin that is used when building new pipx installs.

During the pipipxx install, the python binary that is set for the pipx pipx install correctly points to the brew python, but when pipx install commands are run, pipx attempts to use the ~/.local/pipx/shared/bin/python for some operations.

The way I worked around this was to change the ~/.local/pipx/shared/bin/python symlink to point to the brew python bin, but I need to figure out what pipx is setting now that is creating this other shared bin, and how to override that during the bootstrapping process.