tech-pkg archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
bin/*.py files
I have a series of packages that like to install executable files with *.py names. It seems that the extension is not helpful, other than to match the upstream distribution. From a user perspective it makes remembering the name of commands more complicated, because most do not have such extensions.
What is best practice here? Should we follow upstream (i.e., with *.py extensions) or more standard Unix command name convention (i.e., without *.py extensions)?
Thanks for your thoughts.
Cheers,
Brook
Home |
Main Index |
Thread Index |
Old Index