➜

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 caveman, eric.smith, louielu, paul.j3
Date 2017-10-12.19:48:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content
As documented in many other issues, the usage formatter is brittle.  It formats the individual usages, joins them into a string. Then if too long to fit on one line it tries t split into actions, etc.  This split produces an assertion error if there are 'wierd' characters in the names (e.g. #[]).

With mutually exclusive groups it gets even worse.  The brackets and | are spliced into the original string, and then excess [] and spaces are removed.  Once recent issue complained about its handling of nested groups (which are borderline wrong).

So I"m not surprised that a long group that spans a couple of lines gets messed up.   It requires a major rewrite, and even then I there will be formats involving groups that fall through the cracks.
History
Date User Action Args
2017-10-12 19:48:11paul.j3setrecipients: + paul.j3, eric.smith, louielu, caveman
2017-10-12 19:48:11paul.j3setmessageid: <[email protected]>
2017-10-12 19:48:11paul.j3linkissue31768 messages
2017-10-12 19:48:11paul.j3create