Open aantn opened 3 months ago
It looks like pipx install
with --suffix
is what you need. I use that to install different versions of pipx for test when developing.
Nice, thank you. I can make it work with that. (Although it would be wonderful to have a solution with pipx run too! That lets me simplify the workflow a lot.)
Will --pip-args='--upgrade'
be helpful? Actually, I have not tried it yet.
No, it doesn't work when run twice in a row. (But if you run it once without --pip-args='--upgrade'
and once with --pip-args='--upgrade'
then it does work because that bypasses the cache.)
No, it doesn't work when run twice in a row.
I am a little confused. Could you provide a minimal reproducible example (or a real one)?
Sure, I've recorded a 2 minute video showing this.
When using
pipx run git+...
I seem to have two options:--no-cache
and install the entire virtualenv from scratch--no-cache
and use whatever git version was latest when I first ranpipx run
(potentially several days ago)Is there an alternative where I can reuse the virtualenv but for pipx/pip to always try to upgrade from the latest in git?
There might be a way I can do this with
pipx install
so I'd love to hear alternatives. But please note that I need to have multiple versions of the same repo installed side by side simultaneously (from different branches). (I'm using pipx inside a testing framework to test versions side by side.)Thanks!