[issue46700] wrong nomenclature (options vs. arguments) in argparse

2022-02-12 Thread mirabilos
mirabilos added the comment: Hm, the change helps indeed. I did this in my code: p = argparse.ArgumentParser(description='…', add_help=False) g = p.add_argument_group('Options') g.add_argument('-h', action='help', help='show this help message and exit') g.add_argument(……… g

[issue46700] wrong nomenclature (options vs. arguments) in argparse

2022-02-12 Thread Raymond Hettinger
Raymond Hettinger added the comment: Éric is correct. There is not much that can be done about this. The nomenclature is deeply baked into the code and the docs. We did change the help output to list "options" rather than "optional arguments". That helps the end users so that "optional" do

[issue46700] wrong nomenclature (options vs. arguments) in argparse

2022-02-12 Thread Éric Araujo
Éric Araujo added the comment: I’m afraid this is a basic decision of argparse, and one of its reasons for existing as an rework of optparse. -- nosy: +eric.araujo ___ Python tracker

[issue46700] wrong nomenclature (options vs. arguments) in argparse

2022-02-09 Thread mirabilos
New submission from mirabilos : The argparse documentation and tutorial as well as its default option groups speak of "positional arguments" and "optional arguments". These are not used correctly, though. Elements of the argument vector (past item #0) are distinguished as options and (positio