$PIPX_HOME contain HARD separator - SPACE in the ".../Application Support/..." via HomeBrew

[ucomru]

There are so many open issues with same trouble:

• Bad interpreter /Users/USER/Library/Application: no such file ... #1226
• Injected shebang does not escape whitespace in interpreter path #1212
• $PIPX_HOME on macOS since release 1.3.0 breaks awscli #1198

There are so many things and answers, but the problem in the header of the python venv:

#!/Users/USER/Library/Application Support/pipx/venvs/<some_app>/bin/python

As Im understanding the header of the bin/python: #!/.../bin/python could not to contain symbol.
symbol is interpreted as HARD separator.

According to the pipx environment, the main problem with the $PIPX_HOME.

On MacOS with HomeBrew PIPX_HOME = /Users/USER/Library/Application Support/pipx
It's containing SPACE.

I think the best way is to set linux like variable: PIPX_HOME=$HOME/.local/pipx

It's correcting head links #!/.../bin/python.

When Im using:

export PIPX_HOME=$HOME/.local/pipx

the header at .local/bin/<some_app> is going to the:

#!/Users/USER/.local/pipx/venvs/<some_app>/bin/python
...

Its work fine, and PIPX_HOME=$HOME/.local/pipx is looks more canonical ;-)

[Gitznik]

Hi @ucomru,

thanks raising this. We are aware of this issue and there is an open issue to fix this: #1257.
Indeed, export PIPX_HOME=$HOME/.local/pipx seems like the best way to fix this right now as a user.

[ucomru]

Hi @ucomru,

thanks raising this. We are aware of this issue and there is an open issue to fix this: #1257. Indeed, export PIPX_HOME=$HOME/.local/pipx seems like the best way to fix this right now as a user.

Thanks a lot!