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
While editing a local script in an IDE, the path to the virtualenv or python needs to be provided (for linting & autocompletions).
The virtualenv needs to have the dependencies installed as it is not a typical pyproject.toml or setup.py based project, and thus cannot be managed by IDEs.
Proposed idea:
Add a new flag --print-python-path to pipx run
Check if this flag is set in the function pipx.commands.run.run_script and skip calling any exec_app but instead print the path to python executable (to stdout) and exit
(The above idea is inspired by rust-script's --package option)
Alternatives:
Print a parsable output for --verbose option and add --dry-run option.
The text was updated successfully, but these errors were encountered:
This is within the context of using
pipx run
While editing a local script in an IDE, the path to the virtualenv or python needs to be provided (for linting & autocompletions).
The virtualenv needs to have the dependencies installed as it is not a typical pyproject.toml or setup.py based project, and thus cannot be managed by IDEs.
Proposed idea:
--print-python-path
topipx run
pipx.commands.run.run_script
and skip calling anyexec_app
but instead print the path to python executable (to stdout) and exit(The above idea is inspired by
rust-script
's--package
option)Alternatives:
--verbose
option and add--dry-run
option.The text was updated successfully, but these errors were encountered: