You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issue tracker and believe that this is not a duplicate.
I discover this problem by using PDM with pdm-venv on MacOS. The default virtualenvs directory on MacOS is ~/Library/Application Support/pdm/venvs. And this reveals the bug under the installer code of PDM.
I discover this problem by using PDM with pdm-venv on MacOS. The default virtualenvs directory on MacOS is
~/Library/Application Support/pdm/venvs
. And this reveals the bug under the installer code of PDM.pdm/pdm/installers/installers.py
Lines 49 to 54 in a2098b4
The
ScriptMaker._get_shebang
assumes the executable path is taken care of by the caller. So the path is not enquoted.https://github.com/vsajip/distlib/blob/4f54a3117db58f6bb00c69ab9a892170b91acd3b/distlib/scripts.py#L160-L162
I will create a pull request for resolving this issue via passing the enquoted executable path to
ScriptMaker
.Steps to reproduce
Actual behavior
fail to run due to the corrupted script generated by the un-enquoted exetuable path.
Expected behavior
run success
Environment Information
The text was updated successfully, but these errors were encountered: