Based on the discussion linked below, updating the project definition in pyproject.toml may eliminate the need to build and manually package root-painter for distribution. This could enable direct installation of the root-painter GUI to the system launcher via pip install. Windows compatibility requires verification, but this simplifies user installation.
https://discuss.python.org/t/whats-the-status-of-scripts-vs-entry-points/18524/9
The files specified in scripts will end up in the wheel as-is at <project>-<version>.data/scripts/... These will end up in the bin directory of a Python virtual environment.
The entry_points specified in console_scripts will end up in a .txt file in the metadata folder (.dist-info) within the wheel. The latter get launcher files generated for them by the installer (i.e. pip) in a cross-platform manner.
This change could also remove the need to build a deb package, potentially broadening availability to system launchers beyond Debian.
Based on the discussion linked below, updating the project definition in
pyproject.tomlmay eliminate the need to build and manually packageroot-painterfor distribution. This could enable direct installation of theroot-painterGUI to the system launcher viapip install. Windows compatibility requires verification, but this simplifies user installation.https://discuss.python.org/t/whats-the-status-of-scripts-vs-entry-points/18524/9
This change could also remove the need to build a
debpackage, potentially broadening availability to system launchers beyond Debian.