[issue13824] argparse.FileType opens a file and never closes it

2019-08-28 Thread sebix
Change by sebix : -- nosy: +sebix ___ Python tracker <https://bugs.python.org/issue13824> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue34999] copy.copy and deepcopy do return same logger objects in 3.7

2018-10-18 Thread sebix
sebix added the comment: > I suggest as a workaround that a context manager approach could be used to > save and restore part of the logging configuration around various operations > (at least levels and handlers), as outlined here: > https://docs.python.org/3/howto/logging-c

[issue34999] copy.copy and deepcopy do return same logger objects in 3.7

2018-10-17 Thread sebix
sebix added the comment: Oh, that's something different than I initially thought. Using copy.deepcopy gives the same result as with copy.copy. -- title: Different behavior of copied loggers in 3.7 -> copy.copy and deepcopy do return same logger objects in 3.7 type: -&g

[issue16468] argparse only supports iterable choices

2018-10-16 Thread sebix
Change by sebix : -- nosy: +sebix ___ Python tracker <https://bugs.python.org/issue16468> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue16878] argparse: positional args with nargs='*' defaults to []

2018-10-16 Thread sebix
Change by sebix : -- nosy: +sebix ___ Python tracker <https://bugs.python.org/issue16878> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue9625] argparse: Problem with defaults for variable nargs when using choices

2018-10-16 Thread sebix
Change by sebix : -- nosy: +sebix ___ Python tracker <https://bugs.python.org/issue9625> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue34999] Different behavior of copied loggers in 3.7

2018-10-16 Thread sebix
New submission from sebix : For the unittests of project I mock the function returning the logger. The code to tests can re-initialize the logger because of updated configuration (It's a deamon), so it needs to do that correctly and I test if it works. By mocking the function returning

[issue9338] argparse optionals with nargs='?', '*' or '+' can't be followed by positionals

2018-10-16 Thread sebix
Change by sebix : -- nosy: +sebix ___ Python tracker <https://bugs.python.org/issue9338> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth