Eric McDonald added the comment:
Yes, this issue could be closed. I think the concept is still valid and perhaps
worthy of future consideration as it is a means of unifying two different
configuration processing mechanisms in the standard library without having
developers reinvent that wheel
Eric McDonald added the comment:
@paul.j3, thanks for the sample code for argparse extension. I agree that
subclassing is a way to go for use in third-party projects. But, if someone
ever wanted to add an abstraction layer in front of argparse.ArgumentParser and
configparser.ConfigParser in
New submission from Eric McDonald:
There are several use cases for having the equivalent of the
optparse.OptionParser 'get_option' method and the 'option_groups' and
'option_list' properties in argparse.ArgumentParser class.
(1) Easy alteration of the text of
