[issue36863] argparse doesn't like options in the middle of arguments

paul j3 added the comment: This is intended behavior of multi-nargs positionals. The 'one' string is consumed by the 'file' argument, and there's no positional argument left to consume the other strings. The topic was raised and discussed previously https://bugs.python.org/issue14191

[issue36863] argparse doesn't like options in the middle of arguments

rhubarbdog x added the comment: I've just done a test and from a command shell (bash or whatever) the following python script when ran produces the following $ python3 command.py 0ne thwo three files: ['0ne', 'thwo', 'three'] sensors 1 freq 1200 $ python3 command.py -s 5 0ne thwo three

[issue36863] argparse doesn't like options in the middle of arguments

Martin Panter added the comment: The “cmd” module doesn’t use “argparse” as far as I can see. You might have to provide more information or code for someone to make sense of or reproduce your bug. Also, see Issue 14191 which added new “parse_[known]_intermixed_args” APIs in 3.7, and have a

[issue36863] argparse doesn't like options in the middle of arguments

Change by Glenn Linderman : -- nosy: +v+python ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36863] argparse doesn't like options in the middle of arguments

Change by Larry Hastings : -- nosy: -larry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36863] argparse doesn't like options in the middle of arguments

rhubarbdog x added the comment: This is when running is a shell which inherits from cmd.Cmd -- ___ Python tracker ___ ___

[issue36863] argparse doesn't like options in the middle of arguments

Change by SilentGhost : -- components: +Library (Lib) -Argument Clinic stage: -> test needed type: -> behavior versions: +Python 3.7, Python 3.8 ___ Python tracker ___

[issue36863] argparse doesn't like options in the middle of arguments

New submission from rhubarbdog x : I've found a bug with argparse and reported it upstream. `command --option source destination` works `command soucre destination --option` works but `command source --option destination` doesn't outputting the usage text block associated `do_command` method