Message 274334 - Python tracker

➜

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	Gieskanne, paul.j3
Date	2016-09-04.04:00:53
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1472961654.08.0.233854851546.issue27927@psf.upfronthosting.co.za>
In-reply-to

Content
http://bugs.python.org/issue21633 also deals with the formatter of subparsers. I note there that few of parameters of the main parser propagate to the subparsers. The current design gives the programmer maximum control, at the expense of a bit of typing. If I had to create a large number of subparsers, I might write a utility function to take care of the repetitious tasks.

http://bugs.python.org/issue21633

also deals with the formatter of subparsers.  I note there that few of parameters of the main parser propagate to the subparsers.  

The current design gives the programmer maximum control, at the expense of a bit of typing.  If I had to create a large number of subparsers, I might write a utility function to take care of the repetitious tasks.

History
Date	User	Action	Args
2016-09-04 04:00:54	paul.j3	set	recipients: + paul.j3, Gieskanne
2016-09-04 04:00:54	paul.j3	set	messageid: <1472961654.08.0.233854851546.issue27927@psf.upfronthosting.co.za>
2016-09-04 04:00:54	paul.j3	link	issue27927 messages
2016-09-04 04:00:53	paul.j3	create