# HG changeset patch# User Florent Pigout <email@example.com># Date 1361875069 -3600# Node ID 078bf2f6f5ad5eb9e4b25a8be97f979651fc7146# Parent 0a83b414254454ff0598c566ffdb8b681fbb6316
add global command usage #25
diff -r 0a83b4142544 -r 078bf2f6f5ad baker.py
--- a/baker.py Tue Feb 2611:36:25 2013 +0100
+++ b/baker.py Tue Feb 2611:37:49 2013 +0100
@@ -394,6 +394,12 @@
:param scriptname: the name of the script being executed (argv).
:param fobj: the file to write the help to. The default is stdout.
"""++ self.write(fobj, "\n".join(self.return_cmd_doc(self.globalcommand)))+ self.write(fobj, "\n".join(self.return_argnames_doc(self.globalcommand)))+ self.write(fobj, "\n".join(self.return_keyword_doc(self.globalcommand)))+ self.write(fobj, "\n")+ # Print the basic help for running a command self.write(fobj, "Usage: %s COMMAND <options>\n\n" % scriptname)
Sorry for this ugly comment, worse than that it breaks the tests. So, I just fork baker to send you a nicer patch here.
I really like this way to manage command line apsi, and I would like to generate a debian package of my company, and my next command line Rest Client. But I really need this feature in a coming soon release, otherwise colleagues will have the last word and I will need to refactor my poc with a basic argparse mechanism :/
I hope you will read this comment soon ...