[issue6535] optparse required field for Options

2009-07-21 Thread Daniel Kaplun
Daniel Kaplun added the comment: I have not a single clue how to unit test. What do you mean by documentation patch? Do you want me to update the documentation within the file to reflect changes? -- ___ Python tracker <http://bugs.python.

[issue6535] optparse required field for Options

2009-07-21 Thread Daniel Kaplun
Changes by Daniel Kaplun : Added file: http://bugs.python.org/file14530/testcase.py ___ Python tracker <http://bugs.python.org/issue6535> ___ ___ Python-bugs-list mailin

[issue6535] optparse required field for Options

2009-07-21 Thread Daniel Kaplun
Changes by Daniel Kaplun : -- keywords: +patch Added file: http://bugs.python.org/file14529/optparse.py.diff ___ Python tracker <http://bugs.python.org/issue6

[issue6535] optparse required field for Options

2009-07-21 Thread Daniel Kaplun
Changes by Daniel Kaplun : -- type: -> feature request ___ Python tracker <http://bugs.python.org/issue6535> ___ ___ Python-bugs-list mailing list Unsubscri

[issue6535] optparse required field for Options

2009-07-21 Thread Daniel Kaplun
New submission from Daniel Kaplun : In the second example to allow usage of the required field for options, it seems as if you already have all you need to implement the feature into optparse. I modified it a bit to allow OptionGroups: class Option(optparse.Option): ATTRS