Use the console_scripts entry point to add the command-line tool to path rather than a symlink (for cross-platform compatibility with anything other than *nix).
Use [the console_scripts entry point](https://python-packaging.readthedocs.io/en/latest/command-line-scripts.html#the-console-scripts-entry-point) to add the command-line tool to path rather than a symlink (for cross-platform compatibility with anything other than *nix).
It is imperative that all code contributed be legitimately free software. For that reason, code from anonymous (or pseudonymous) contributors will not be accepted.
Regardless, I strongly dislike how console_scripts requires a main() function. I don't want main to be callable by a different program (perhaps a UI program) which imports libray as a dependency.
It is imperative that all code contributed be legitimately free software. For that reason, code from anonymous (or pseudonymous) contributors will not be accepted.
Regardless, I strongly dislike how console_scripts requires a main() function. I don't want main to be callable by a different program (perhaps a UI program) which imports libray as a dependency.
Use the console_scripts entry point to add the command-line tool to path rather than a symlink (for cross-platform compatibility with anything other than *nix).
It is imperative that all code contributed be legitimately free software. For that reason, code from anonymous (or pseudonymous) contributors will not be accepted.
Regardless, I strongly dislike how console_scripts requires a main() function. I don't want main to be callable by a different program (perhaps a UI program) which imports libray as a dependency.