[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Change by Eryk Sun : -- Removed message: https://bugs.python.org/msg405700 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Change by Eryk Sun : -- components: +Library (Lib) -Subinterpreters nosy: -ahmedsayeed1982 versions: +Python 3.7 -Python 3.8 ___ Python tracker ___

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Ahmed Sayeed added the comment: $ ../gdb -nx --data-directory=../data-directory (gdb) set osabi GNU/Linux http://www.compilatori.com/category/technology/ (gdb) set sysroot /home/simark/build/binutils-gdb/gdb/repo (gdb) file Foo

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Roundup Robot added the comment: New changeset 459500606560 by Vinay Sajip in branch 'default': Closes #28524: added default level for logging.disable(). https://hg.python.org/cpython/rev/459500606560 -- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Al Sweigart added the comment: Setting up different configurations for dev/prod is a bit more complicated than I'd like for most projects. I'd instead just call logging.disable(logging.CRITICAL). The entire point of this is just for the convenience of being able to disable logging messages

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Vinay Sajip added the comment: > The use case I've found is that I often have logging enabled while writing > code, and then want to shut it off once I've finished. You could do this by having a configuration which is quite verbose while doing development and then less verbose when in

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Changes by Raymond Hettinger : -- assignee: -> vinay.sajip priority: normal -> low versions: +Python 3.7 ___ Python tracker

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Al Sweigart added the comment: As a general indicator, I did a google search for "logging.disable(logging.XXX)" for the different levels. The number of results passing ERROR, WARN, DEBUG, and INFO are under a couple dozen each. But the number of results for "logging.disable(logging.CRITICAL)"

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Raymond Hettinger added the comment: Put me down for -0. I don't think the minor convenience is worth the loss in clarity. -- ___ Python tracker ___

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Al Sweigart added the comment: > How about logger.disabled = True. This seems to violate "there should be one and only one way to do it". What happens when logging.disabled is True but then logging.disable(logging.NOTSET) is called? I could see this being a gotcha. Since logging.CRITICAL is

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Xiang Zhang added the comment: > We could use sys.maxsize instead of logging.CRITICAL to disable any custom > logging levels as well if this is a concern. sys.maxsize is not the upper bound limit of integers in Python. There is no such value in Python3. > The use case I've found is that I

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Al Sweigart added the comment: xiang.zhang: The use case I've found is that I often have logging enabled while writing code, and then want to shut it off once I've finished. This might not be everyone's use case, but this is a backwards-compatible change since it's currently a required

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Raymond Hettinger added the comment: Given that a user can add their on levels, I think that having a default would be misleading (having no arguments implies total disabling but with custom levels the default of CRITICAL might not disable all messages). -- nosy: +rhettinger

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Xiang Zhang added the comment: Is disabling all logging messages a common need? Maybe other levels are common but we can't know. And at least the doc patch needs a versionchanged tag. -- nosy: +xiang.zhang ___ Python tracker

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

Changes by Ned Deily : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list

[issue28524] Set default argument of logging.disable() to logging.CRITICAL

New submission from Al Sweigart: As a convenience, we could make the default argument for logging.disable()'s lvl argument as logging.CRITICAL. This would make disabling all logging messages: logging.disable() ...instead of the more verbose: logging.disable(logging.CRITICAL) This one-line