entry-point script and private module install directory
Dear all,
I have a package (pyfr), which is meant to be used as a command-line
application only.
The main script (pyfr) is installed via setuptools'
entry_points['console_scripts'], which generates the entry-point
automatically and places it under /usr/bin. However, when I install the
implementation module in a private location, such as /usr/share/pyfr,
the entry-point cannot find the module and load the application.
Right now, the module is installed in the dist-packages location,
although it is not intended to be public. It was just the easiest
solution to start with at the time.
What is the standard way to circumvent this? Do other packages use
custom wrapper scripts, or is there a more clever way to tell the
entry-point to look for a custom package location? Is there a good
example you guys can point me to?
There was a similar discussion for the grip [1] package on this list,
but it did not lead to something I can use, or so I believe.
[1] https://lists.debian.org/debian-python/2016/04/msg00001.html
Many thanks,
Ghis
Reply to: