[issue6535] optparse required field for Options

Georg Brandl added the comment: I don't think optparse will get this update -- new features should go into argparse instead. -- nosy: +georg.brandl resolution: -> out of date status: open -> closed ___ Python tracker

[issue6535] optparse required field for Options

R. David Murray added the comment: Well, if you get check out the current trunk via svn (as described in the developer's faq linked from http://www.python.org/dev) and you look at what Lib/test/test_optparse.py currently does, you might find it is not too hard to add some new cases to test the n

[issue6535] optparse required field for Options

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

[issue6535] optparse required field for Options

R. David Murray added the comment: What we are looking for in the way of tests is unit tests to add to test_optparse. Another piece that I forgot about that we'll need is a documentation patch. Finally, it will be easier to review the patch if you don't make other changes in the patch. Your P

[issue6535] optparse required field for Options

Changes by Daniel Kaplun : Added file: http://bugs.python.org/file14530/testcase.py ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue6535] optparse required field for Options

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

[issue6535] optparse required field for Options

R. David Murray added the comment: Feature requests can only go into releases under development. No guarantees, but if you want to give this a better chance of getting in a patch against trunk including tests would be a minimum prerequisite. Alternatively or in addition you could help review a

[issue6535] optparse required field for Options

Changes by Daniel Kaplun : -- type: -> feature request ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue6535] optparse required field for Options

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 = optparse.Opti