Kitware
Entry point scripts should have more consistent flags/functionality
The most glaring example being some take a list of globs for files to work on, while others take a path to a filename containing the files to work on.
If there's some underlying convention I'm not seeing, feel free to close this out.
Not exactly addressing your specific example, but I tried to do some standardization with CLI options via the smqtk.utils.bin_utils.utility_main_helper.
As for file-list or CLI-specified globs, I think the original intention was that the utility that uses globs was meant for a smaller number of files where as the file-list ones assumed the possibility of larger data-sets. If I were to pick just one for standardization, I would go with the file list.
If that's the case, it would be nice if the file list supported bash-style fifos i.e. compute_classifications --file-list <(find ...) to easily switch between the 2. Currently they use os.path.isfile and that doesn't like a path to /proc/PID/fd.
FWIW, #287 has support for bash-style fifos by just checking if the path exists. If the user passes a directory instead, the script throws an "IOError: Is a directory" when trying to read from it, which I think is pretty clear.