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 a project that has an option command line interface, which can be installed via pip install lib[cli]
This is not a big deal, but I was wondering if pipx could support a default group for when running/installing a library, so users would only need to run pipx run lib (or pipx install lib)
This would remove some friction in using the cli from my library, and also prevent some small issue like quoting (some shells don't like the [] syntax 😊)
Maybe pipx could check if there's a cli group, or maybe we can add some metadata on the package?
Not sure if all of these are feasible 😊
Another option on myside would be to check if the dependencies are missing and tell the user to run install/run lib[cli], but I'd like to avoid one extra step if possibile 😊
The text was updated successfully, but these errors were encountered:
This is not a big deal, but I was wondering if pipx could support a default group for when running/installing a library, so users would only need to run pipx run lib (or pipx install lib)
Hmm, you mean whenever installing a library, a cli extra should be installed? AFAIK, there is no such standard that a library should expose its CLI interface via an extra called that way? I do think the behaviour that we have right now is correct, and if I understand you correctly, the only way to detect an entry point within a library would be searching amongst its extras, which I think is a bit overshooting.
@chrysle just to clarify, I don't think pipx is doing anything wrong, I was just thinking if there's a way to make the experience better in some cases 😊
the only way to detect an entry point within a library would be searching amongst its extras, which I think is a bit overshooting.
Yeah probably, I wonder if there's something we can add in the package metadata for that? Also maybe it could be better to use a pipx group, so there are less potential issues?
Also, I'm totally fine with closing this issue if you don't think is a good addition :D
Hi there!
I have a project that has an option command line interface, which can be installed via
pip install lib[cli]
This is not a big deal, but I was wondering if
pipx
could support a default group for when running/installing a library, so users would only need to runpipx run lib
(orpipx install lib
)This would remove some friction in using the cli from my library, and also prevent some small issue like quoting (some shells don't like the
[]
syntax 😊)Maybe pipx could check if there's a
cli
group, or maybe we can add some metadata on the package?Not sure if all of these are feasible 😊
Another option on myside would be to check if the dependencies are missing and tell the user to run
install/run lib[cli]
, but I'd like to avoid one extra step if possibile 😊The text was updated successfully, but these errors were encountered: