[issue40509] In argparse, allow REMAINDER(...) arguments in a mutually exclusive group

2020-05-19 Thread Shani Armon
Shani Armon added the comment: Bumping, since no reply was made to my previous comment. If this is not relevant at all can this be closed or marked as such, so that it may be raised in python-dev? -- ___ Python tracker <https://bugs.python.

[issue40509] In argparse, allow REMAINDER(...) arguments in a mutually exclusive group

2020-05-06 Thread Shani Armon
Shani Armon added the comment: Also, this is quite different from previous issues with REMAINDER. This fits in line with how the example suggests remainder should be used. I wand some flags (version, configuration) to be separate and exclusive to subcommands. And the usage is not ambiguous

[issue40509] In argparse, allow REMAINDER(...) arguments in a mutually exclusive group

2020-05-06 Thread Shani Armon
Shani Armon added the comment: Yes. The pull request contains the special handling. For the purpose of REMAINDER positionals, the default is changed to the empty list that was returned if no arguments were passed. For the purpose of positional argument, that is equivalent to nothing being

[issue40509] In argparse, allow REMAINDER(...) arguments in a mutually exclusive group

2020-05-05 Thread Shani Armon
Shani Armon added the comment: Why is REMAINDER any more complicated than ZERO_OR_MORE? I need to make a subcommand system (think jupyter style) and -- isn't an intuitive interface. Jupyter just doesn't use argparse in the subcommand case. I prever to in order to support opt

[issue40509] In argparse, allow REMAINDER(...) arguments in a mutually exclusive group

2020-05-05 Thread Shani Armon
Change by Shani Armon : -- keywords: +patch pull_requests: +19233 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19919 ___ Python tracker <https://bugs.python.org/issu

[issue40509] In argparse, allow REMAINDER(...) arguments in a mutually exclusive group

2020-05-05 Thread Shani Armon
New submission from Shani Armon : Options specified with the REMAINDER nargs should be treated as optional. And an empty list should be treated as default. -- components: Library (Lib) messages: 368126 nosy: Shani Armon, rhettinger priority: normal severity: normal status: open title

[issue39597] sorting the String

2020-02-10 Thread Shani M
New submission from Shani M : It showing the wrong string order. 'sss' is to be appear at 3rd place but it comes at last place. 'qwe' is to appear at last place but it comes at 3rd place. -- files: Screenshot from 2020-02-10 14-08-52.png messages: 361675 nosy: Shan

[issue23267] multiprocessing pool.py doesn't close inqueue and outqueue pipes on termination

2015-01-18 Thread shani
New submission from shani: Multiprocessing pool.py gets SimpleQueue objects as inqueue and outqueue. when it terminates, it doesn't call the close() method of the queues' readers and writers. As a results, 4 file pipes leak in one pool termination. Expected: The pool closes reader