> Od: Ben Finney <email@example.com>
MP> > Stick zynjacku.py in a proper library path somewhere, and write a
MP> > little shim wrapper to stick in /usr/bin that calls zynjacku as it
MP> > expects to be called.
BF> Yes, that's one way to do it, and quite valid. It does, though, involve
BF> creating that shim separately after installing the distribution.
BF> IIUC, the ‘entry_points’ facility (of the third-party ‘pkg_resources’
BF> module) is another way, that allows the program file to be created
BF> automatically, such that when run it will invoke a specified function,
BF> along with the rest of the distribution's installation process.
Any link where I can study more to understand and solve problem?