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
The documentation on how pipx works (https://pypa.github.io/pipx/how-pipx-works/) suggests that only functions defined in entry_points as console_scripts are available to pipx after installation.
Having functions defined as gui_scripts available, too, would allow to use pipx for GUI applications.
Describe the solution you'd like
When gui_scripts are defined as entry_points in setup.py, pipx should make those available as known commands on the system.
Describe alternatives you've considered
The alternative seems to be to specify GUI applications as console_scripts, which would always open a terminal when run from a place other than a terminal.
The text was updated successfully, but these errors were encountered:
It could be, I’m not familiar with the exact behaviour either. Could you try locally whether gui_scripts are indeed correctly handled already, and if so, draft some documentation fixes?
How would this feature be useful?
The documentation on how pipx works (https://pypa.github.io/pipx/how-pipx-works/) suggests that only functions defined in
entry_points
asconsole_scripts
are available to pipx after installation.Having functions defined as
gui_scripts
available, too, would allow to use pipx for GUI applications.Describe the solution you'd like
When
gui_scripts
are defined asentry_points
insetup.py
, pipx should make those available as known commands on the system.Describe alternatives you've considered
The alternative seems to be to specify GUI applications as
console_scripts
, which would always open a terminal when run from a place other than a terminal.The text was updated successfully, but these errors were encountered: