[issue41600] Expected behavior of argparse given quoted strings

Vegard Stikbakke added the comment: Great idea, thanks! It's open source, so I'll see if I can fix it. On Thu, 20 Aug 2020 at 17:28, Eric V. Smith wrote: > > > Eric V. Smith added the comment: > > > > Completely agree with paul j3. The calling tool is breaki

[issue41600] Expected behavior of argparse given quoted strings

Vegard Stikbakke added the comment: I see! Thanks, had not heard about shlex. I also had not realized `parse_args` takes arguments. Doh. That makes sense. Thanks a lot! -- ___ Python tracker <https://bugs.python.org/issue41

[issue41600] Expected behavior of argparse given quoted strings

Vegard Stikbakke added the comment: In fact, what happens in the latter case (i.e. `"--a 1 --b 2"`), inside the call to `_parse_optional`, is that it fails to get the optional tuple. And so it continues to this line in argparse.py: https://github.com/python/cp

[issue41600] Expected behavior of argparse given quoted strings

Vegard Stikbakke added the comment: It seems that I mixed up something in the post here. If the quoted string is `"--a=1 --b=2` as I said in the post, then the program will only complain about `b` missing. In this case, it sets `a` to be `1 --b=2`. Whereas if the quoted string is `&

[issue41600] Expected behavior of argparse given quoted strings

Vegard Stikbakke added the comment: For what it's worth, I'd love to work on this if it's something that could be nice to have. -- ___ Python tracker <https://bugs.pyt

[issue41600] Expected behavior of argparse given quoted strings

New submission from Vegard Stikbakke : I'm not sure if this is a bug, but I had a problem when I was trying to use argparse recently, and I was wondering about the expected behavior. For context: We invoke a Python program from a deployment tool, where we provide input in a text box. We

[issue38932] unittest.mock.Mock.reset_mocks does not pass all arguments to its children

Vegard Stikbakke added the comment: Oh, right! Thanks! -- ___ Python tracker <https://bugs.python.org/issue38932> ___ ___ Python-bugs-list mailing list Unsub

[issue38932] unittest.mock.Mock.reset_mocks does not pass all arguments to its children

Change by Vegard Stikbakke : -- keywords: +patch pull_requests: +16889 stage: -> patch review pull_request: https://github.com/python/cpython/pull/17409 ___ Python tracker <https://bugs.python.org/issu

[issue38932] unittest.mock.Mock.reset_mocks does not pass all arguments to its children

Change by Vegard Stikbakke : -- versions: -Python 3.7 ___ Python tracker <https://bugs.python.org/issue38932> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38932] unittest.mock.Mock.reset_mocks does not pass all arguments to its children

Vegard Stikbakke added the comment: I said MagicMock, but I meant Mock. -- ___ Python tracker <https://bugs.python.org/issue38932> ___ ___ Python-bugs-list m

[issue38932] unittest.mock.Mock.reset_mocks does not pass all arguments to its children

Change by Vegard Stikbakke : -- title: MagicMock.reset_mocks does not pass all arguments to its children -> unittest.mock.Mock.reset_mocks does not pass all arguments to its children ___ Python tracker <https://bugs.python.org/issu

[issue38932] MagicMock.reset_mocks does not pass all arguments to its children

New submission from Vegard Stikbakke : MagicMock, from unittest.mock, has a method reset_mock, which takes optional arguments return_value and side_effect, both with default values False. In the body of reset_mock, reset_mock is again called on all the _mock_children of of the MagicMock

[issue1751519] curses - new window methods: addchstr and addchnstr

Vegard added the comment: Bump, I just found out addchstr() is unsupported, which is unfortunate as there doesn't seem to be any other easy way to prevent line wrapping if you submit too long strings to addstr() without keeping track of the x location and/or the string length by