Use click
I prefer docopt. For small/quick tools I find it to be the easiest.
Nothing to do with CLI apps in particular, just some packaging best practices, if even that. Aren’t there a hundred tutorials for this?
Don’t reinstall over and over, just use ./setup.py develop. And do it in a virtualenv.
There is no such thing as packaging best practices for everything. Having this amount of boilerplate for a CLI app is a case study in over-engineering.
If only there were a package in the python standard library for handling command line arguments…
Do you mean that you don’t consider argparse or getopt good enough for the standard library? Or maybe you were ironic?
I was being facetious :)
I see :P
That was what I expected this to be about, not “how to package a python application”
Use click
I prefer docopt. For small/quick tools I find it to be the easiest.
Nothing to do with CLI apps in particular, just some packaging best practices, if even that. Aren’t there a hundred tutorials for this?
Don’t reinstall over and over, just use ./setup.py develop. And do it in a virtualenv.
There is no such thing as packaging best practices for everything. Having this amount of boilerplate for a CLI app is a case study in over-engineering.
If only there were a package in the python standard library for handling command line arguments…
Do you mean that you don’t consider argparse or getopt good enough for the standard library? Or maybe you were ironic?
I was being facetious :)
I see :P
That was what I expected this to be about, not “how to package a python application”