On Sep 29, 2009, at 9:18 PM, Nick Coghlan wrote:
Keeping getopt around *and* including a "add_getopt_arguments" method inargparse is probably the best of both worlds, in that it allows for relatively straightforward evolution of an application:1. Start with getopt2. As the getopt argument parsing gets twisty and arcane and maintainingthe help string becomes a nightmare, move to argparse with the "add_getopt_arguments" method. 3. Over time, convert more arguments to proper argparse arguments with full documentation.
Maybe. I haven't been following this entire thread, but I don't see much point in making it easy to go from getopt to argparse. The two are so different that I think you're either going to jump all in or not. Maybe that's just me though as I really don't see much use for getopt any more (even for throwaway scripts).
-Barry
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
