I’ve recently created a Python script that I think can be useful to a lot of organizations. It presently exists as a standalone script which accepts various command line parameters that define the work it will do (e.g. python3 MyUtility.py --param1 something --param2 something).
It’ll be on GitHub shortly. I’d like to have a setup process for it where organizations can use something like PyPI to install it, but I’m not 100% sure PyPI meets all my requirements, which are:
- Install python libraries that are dependencies (that part I know PyPI can do)
- Install applications that are dependencies (e.g. MariaDB)
- After the installation is complete, have it in the path where it can be run at the command line with no extension (so a user can simply type MyUtility --param1 something --param2 something). This could be accomplished by copying it within /bin somewhere or just adding its install location to the path; the Python shebang is already in the script so it works without an extension.
It’s basically used as a command line utility and I can’t imagine a scenario where a script would need to import it. All the packaging examples I’ve encountered so far seem to be geared toward modules you’d be importing rather than something that’s a command-line utility, but maybe I’m not finding good examples.
Does anyone have a suggestion on the best way for me to package something like this for installation?
Thanks in advance.