[issue14856] argparse: creating an already defined subparsers does not raises an exception

Irit Katriel added the comment: The open patch deprecates overriding the parser with add_parser, but it does not add the new set_parser method that Steven suggested. -- nosy: +iritkatriel stage: patch review -> type: -> enhancement versions: +Python 3.11 -Python 3.3 ___

[issue14856] argparse: creating an already defined subparsers does not raises an exception

Braden Groom added the comment: https://github.com/python/cpython/pull/10159 -- nosy: +bradengroom ___ Python tracker ___ ___ Pytho

[issue14856] argparse: creating an already defined subparsers does not raises an exception

Change by Braden Groom : -- pull_requests: +9481, 9482, 9483 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mai

[issue14856] argparse: creating an already defined subparsers does not raises an exception

Change by Braden Groom : -- pull_requests: +9481, 9482 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue14856] argparse: creating an already defined subparsers does not raises an exception

Change by Braden Groom : -- pull_requests: +9481 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue14856] argparse: creating an already defined subparsers does not raises an exception

Steven Bethard added the comment: Yeah, overwriting the existing parser is probably not typically what the user intended. However, I could see someone doing this if, say, they had a parser designed by another module writer, and they wanted to use it but just change one of the sub-parsers or

[issue14856] argparse: creating an already defined subparsers does not raises an exception

R. David Murray added the comment: Thanks for the report and patch. However, since there is no del_parser method, I'm inclined to think that this is not a bug. That is, the ability to overwrite a previously defined subparser could be considered a feature. If Steven does consider it a bug, I

[issue14856] argparse: creating an already defined subparsers does not raises an exception

New submission from Étienne Buira : With this patch, it raises an ArgumentException, instead of overwriting previous subparser without notice. Regards. -- components: Library (Lib) files: argparse_no_dup_subparsers.diff keywords: patch messages: 161112 nosy: eacb priority: normal sever