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 find it really useful to use pipx for managing the user-wide python tools, such as vex.
Installing vex with pipx is slightly more complex than pipx install vex: because vex needs virtualenv as a subprocess, it needs pipx install --include-deps vex, otherwise, the entrypoints of dependencies are not available in the venv vex creates.
Given that pipx is more and more a popular tool among python users, do you think it's worth specifying that in the README?
The text was updated successfully, but these errors were encountered:
I find it really useful to use pipx for managing the user-wide python tools, such as vex.
Installing vex with pipx is slightly more complex than
pipx install vex
: because vex needsvirtualenv
as a subprocess, it needspipx install --include-deps vex
, otherwise, the entrypoints of dependencies are not available in the venv vex creates.Given that
pipx
is more and more a popular tool among python users, do you think it's worth specifying that in the README?The text was updated successfully, but these errors were encountered: