You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It feels like #4 will solve this problem (though a solution for #4 does indeed seem like it will be anything but trivial), but when I try to provide optional arguments to a repeatable subcommand, the indexing makes it impossible to work out which command each argument belongs to.
The following example raises an IndexError on the third iteration because the --speed 999 gets interpreted as part of the second go command rather than the third:
Maybe args['go'] should accumulate arguments and options passed after it? Right now commands are treated same as flag options (they are True/False or counted). However, maybe, they should be treated more like options with arguments? I.e. having other options/arguments as its value?
It feels like #4 will solve this problem (though a solution for #4 does indeed seem like it will be anything but trivial), but when I try to provide optional arguments to a repeatable subcommand, the indexing makes it impossible to work out which command each argument belongs to.
The following example raises an IndexError on the third iteration because the
--speed 999
gets interpreted as part of the secondgo
command rather than the third:The text was updated successfully, but these errors were encountered: