This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author paul.j3
Recipients bethard, memeplex, paul.j3
Date 2016-03-11.00:01:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1457654463.33.0.304362051721.issue26510@psf.upfronthosting.co.za>
In-reply-to
Content
This has been raised before.  I think

http://bugs.python.org/issue9253

is the correct issue.

It used to be that 'subparsers' were required.  But there was a change in how 'required' arguments were tested, and 'subparsers' fell through the cracks.  Now subparsers are optional (at least the parser doesn't raise an error).  The temporary fix is to set the 'required' attribute after creation.

I proposed that the default be 'required=True', and that we be allowed to set the parameter.  But that patch, like many others, has languished.
History
Date User Action Args
2016-03-11 00:01:03paul.j3setrecipients: + paul.j3, bethard, memeplex
2016-03-11 00:01:03paul.j3setmessageid: <1457654463.33.0.304362051721.issue26510@psf.upfronthosting.co.za>
2016-03-11 00:01:03paul.j3linkissue26510 messages
2016-03-11 00:01:03paul.j3create