pipx run compatible entrypoint

[henryiii]

What's the problem this feature will solve?

Improve support for pipx run. Currently, you have to use --spec to to use pipx run, because pip-tools does not contain an executable called pip-tools.

Describe the solution you'd like

Two possibilities:

1. Add pip-tools as a console-script entry point to __main__:cli. Then python -m pip-tools compile could be written as pip-tools compile, and pipx run would be happy.
2. Add a pipx.run entrypoint. The nice thing about this is you could disable pipx run pip-tools sync until sync support is finished (Support for installation via pipx #1087) by providing a modified cli as the entrypoint. Maybe it could even support sync by selecting the correct python?

pipx run is a 'temporary' version of pipx install, which works well for just using what you need when you need it. pipx built-in support might be coming to manylinux soon, which could be a very handy way to run pip-compile.

[ssbarnea]

@henryiii Just make a PR! I am also using pipx myself. Any approach seems reasonable to me.

[henryiii]

Still planning to do this; will need to play around to decide on how to handle "sync".

[AndydeCleyre]

FWIW, zpy's pip-tools-based pipx clone, pipz, always requires the pkgspec when using the analogous subcommand, runpkg, and so the syntax is, in the case where you need --spec for pipx, very slightly shorter:

$ pipz runpkg pip-tools pip-compile
$ pipz runpkg 'pip-tools @ git+https://github.com/atugushev/pip-tools@new-resolver' pip-compile --resolver backtracking