userpath
userpath copied to clipboard
Release v1.9.0 breaks automation use-cases
Hi,
I indirectly use your excellent module, indirectly as I use pipx
. Now, my issue is that when you changed how PATH
is defined. Explicitly this is causing me grief: On non-Windows systems only modify login shells
.
Thus, whenever I do e.g.: ssh foo@bar "my-command"
, then it fails, or when using e.g. Paramiko exec_command("my-command")
. Basically, all forms of "automation" entry-points which uses a tool installed with pipx
and having used pipx ensurepath
to make sure it was available. Since, userpath
no longer populate these, then this all break.
Thus, two questions:
- Why only login-shells to begin with?
- Can this be change be reverted?
Cheers, Simon