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 Krzysztof Leszczyński, josh.r, paul.j3
Date 2018-02-13.03:01:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1518490896.17.0.467229070634.issue32833@psf.upfronthosting.co.za>
In-reply-to
Content
Subparsers have aliases, argument option strings don't, at least not formally.  Once an argument is added, its flags are entered in several lists.  One list belongs to the Action itself, another belongs to the parser (it might actually be a dictionary).  The code could check that '--a-b' and '--ab' belong to the same Action, but I suspect it doesn't, at least not at the point where it is checking for ambiguity.

We can look at the code to verify this.  It is also entirely likely that this issue has already been raised.  There are other issues regarding how it checks for abbreviations (and how to disable abbreviations).
History
Date User Action Args
2018-02-13 03:01:36paul.j3setrecipients: + paul.j3, josh.r, Krzysztof Leszczyński
2018-02-13 03:01:36paul.j3setmessageid: <1518490896.17.0.467229070634.issue32833@psf.upfronthosting.co.za>
2018-02-13 03:01:36paul.j3linkissue32833 messages
2018-02-13 03:01:35paul.j3create