Description
First of all, thank you for creating and maintaining GitFive.
I encountered an issue while installing GitFive using the installation method described in the README.
Environment
- OS: Ubuntu 24.04
- Shell: zsh
- Python: 3.12.3
- pipx: latest available version
Steps to reproduce
pip3 install pipx --break-system-packages
pipx ensurepath
pipx install gitfive --include-deps
Expected behavior
The gitfive command should be available after installation.
Example:
Actual behavior
The installation succeeds without errors, but no gitfive executable is exposed.
pipx list shows:
package gitfive 1.1.10
- f2py
- find_similar_images.py
- httpx
- idna
- markdown-it
- normalizer
- numpy-config
- pygmentize
- unidecode
Notice that only executables from dependencies are exposed, while the gitfive CLI itself is missing.
The virtual environment also does not contain a gitfive executable:
ls ~/.local/share/pipx/venvs/gitfive/bin/
Additional information
The project itself works correctly when executed directly:
which correctly displays:
usage: gitfive [-h] {login,user,email,emails,light} ...
I also noticed that the CLI entry point is currently declared under:
[tool.poetry.scripts]
gitfive = "gitfive.gitfive:main"
Could this be related to the packaging configuration? Since newer packaging standards typically expose CLI entry points through the [project.scripts] section defined by PEP 621, perhaps pipx is not detecting the executable correctly depending on the build backend.
I'm not sure whether this is expected behavior or a packaging issue, but I wanted to report it in case it helps.
Thanks again for the great project!
Description
First of all, thank you for creating and maintaining GitFive.
I encountered an issue while installing GitFive using the installation method described in the README.
Environment
Steps to reproduce
Expected behavior
The
gitfivecommand should be available after installation.Example:
Actual behavior
The installation succeeds without errors, but no
gitfiveexecutable is exposed.pipx listshows:Notice that only executables from dependencies are exposed, while the
gitfiveCLI itself is missing.The virtual environment also does not contain a
gitfiveexecutable:ls ~/.local/share/pipx/venvs/gitfive/bin/Additional information
The project itself works correctly when executed directly:
which correctly displays:
I also noticed that the CLI entry point is currently declared under:
Could this be related to the packaging configuration? Since newer packaging standards typically expose CLI entry points through the
[project.scripts]section defined by PEP 621, perhapspipxis not detecting the executable correctly depending on the build backend.I'm not sure whether this is expected behavior or a packaging issue, but I wanted to report it in case it helps.
Thanks again for the great project!