[issue28210] argparse with subcommands difference in python 2.7 / 3.5

2016-09-28 Thread Mariatta Wijaya
Changes by Mariatta Wijaya : -- nosy: +Mariatta ___ Python tracker ___ ___

[issue28210] argparse with subcommands difference in python 2.7 / 3.5

2016-09-27 Thread paul j3
paul j3 added the comment: Yes there was/is a bug that made subparsers optional. http://bugs.python.org/issue9253 -- nosy: +paul.j3 ___ Python tracker

[issue28210] argparse with subcommands difference in python 2.7 / 3.5

2016-09-21 Thread Tim Graham
Tim Graham added the comment: Based on the usage output, it looks like the subcommand is required, but I'm not sure if there are cases where a subcommand could be optional. David, can you advise? usage: test_argparse.py [-h] command ... -- nosy: +r.david.murray

[issue28210] argparse with subcommands difference in python 2.7 / 3.5

2016-09-21 Thread stephan
stephan added the comment: I am not an expert with argparse since I just started using it (and it has quite a lot of features which are not all self-explaining to me). But if I didn't misunderstand something it should behave like the python 2.7 version: If I do not pass any command I am told

[issue28210] argparse with subcommands difference in python 2.7 / 3.5

2016-09-20 Thread Tim Graham
Tim Graham added the comment: The behavior change is from #10424. Do you believe the new behavior is incorrect? -- nosy: +Tim.Graham ___ Python tracker

[issue28210] argparse with subcommands difference in python 2.7 / 3.5

2016-09-20 Thread stephan
New submission from stephan: In python 2.7.12 I get an error if I do not pass arguments, while in python 3.5.2 I do not get the error (it fails silently). Stumbled on this during my migration of my python 2.7 code to python 3.5 for django. Here is the console output: D:\util\python\test>py -3