In <[EMAIL PROTECTED]> "Reedick, Andrew" <[EMAIL PROTECTED]> writes:
>> Be that as it may, the activation barrier to using Python for my >> scripting remains too high. >>=20 >> I'd written a Perl module to facilitate the writing of scripts. >> It contained all my boilerplate code for parsing and validating >> command-line options, generating of accessor functions for these >> options, printing of the help message and of the full documentation, >> testing, etc. >Bleh. Perl and Python have really good libraries. Why waste time >rolling your own when you can use Python's getopt or optparse, or Perl's >Getopt and Getopt::Long? No, no "bleh". My module in fact uses Getopt::Long behind the scenes, but customizes the heck out of it and adds a ton of functionality I wanted not available in Getopt::Long. kynn -- NOTE: In my address everything before the first period is backwards; and the last period, and everything after it, should be discarded. -- http://mail.python.org/mailman/listinfo/python-list
