+1 for docopt-ng - became my preference several years ago - after I looked at many of the same alternatives. For configuration, I abandoned the common file formats in favor of just using a .py file - usually _config.py in the root of the main package. This allows me to use types and other lightweight behavior in Python itself. All the points you made are valid - but, there is a balance that needs to be realized between all of those features, simplicity and accurate (read maintained) help docs. Thanks for the awesome talk. I, too, came from the K&R C era. Most people do not understand the complexity involved in designing / implementing a robust and rich CLI. All user interfaces are hard! Thanks for highlighting that fact.
❤Excellent talk, very relaxing vibes, thank you!
You know that this guy is an OG when you learn that his projects are hosted on sourceforge.
+1 for docopt-ng - became my preference several years ago - after I looked at many of the same alternatives.
For configuration, I abandoned the common file formats in favor of just using a .py file - usually _config.py in the root of the main package.
This allows me to use types and other lightweight behavior in Python itself.
All the points you made are valid - but, there is a balance that needs to be realized between all of those features, simplicity and accurate (read maintained) help docs.
Thanks for the awesome talk. I, too, came from the K&R C era. Most people do not understand the complexity involved in designing / implementing a robust and rich CLI. All user interfaces are hard! Thanks for highlighting that fact.