loggery 0.3.1__tar.gz

loggery-0.3.1/LICENSE

@@ -0,0 +1,65 @@
+GNU LESSER GENERAL PUBLIC LICENSE
+
+Version 3, 29 June 2007
+
+Copyright © 2007 Free Software Foundation, Inc. <https://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.
+0. Additional Definitions.
+
+As used herein, “this License” refers to version 3 of the GNU Lesser General Public License, and the “GNU GPL” refers to version 3 of the GNU General Public License.
+
+“The Library” refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.
+
+An “Application” is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.
+
+A “Combined Work” is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the “Linked Version”.
+
+The “Minimal Corresponding Source” for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.
+
+The “Corresponding Application Code” for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.
+1. Exception to Section 3 of the GNU GPL.
+
+You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.
+2. Conveying Modified Versions.
+
+If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:
+
+    a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or
+    b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.
+
+3. Object Code Incorporating Material from Library Header Files.
+
+The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following:
+
+    a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.
+    b) Accompany the object code with a copy of the GNU GPL and this license document.
+
+4. Combined Works.
+
+You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:
+
+    a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.
+    b) Accompany the Combined Work with a copy of the GNU GPL and this license document.
+    c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document.
+    d) Do one of the following:
+        0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.
+        1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.
+    e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.)
+
+5. Combined Libraries.
+
+You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following:
+
+    a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License.
+    b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
+
+6. Revised Versions of the GNU Lesser General Public License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation.
+
+If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.

loggery-0.3.1/PKG-INFO

@@ -0,0 +1,135 @@
+Metadata-Version: 2.3
+Name: loggery
+Version: 0.3.1
+Summary: Configure logging with reduced noise from spammy modules with easy argparse support
+License: LGPL-3.0-or-later
+Author: Erskin Cherry
+Author-email: erskin@eldritch.org
+Requires-Python: >=3.13
+Classifier: Programming Language :: Python :: 3
+Classifier: Operating System :: OS Independent
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: GNU Lesser General Public License v3 or later (LGPLv3+)
+Project-URL: Homepage, https://gitlab.com/frobnic8/loggery
+Project-URL: Repository, https://gitlab.com/frobnic8/loggery
+Description-Content-Type: text/markdown
+
+logsetup
+========
+*Easy and standardized logging for Python*
+
+Log Format
+----------
+This package configures logging with the following format:
+
+    "{asctime} [{levelname}] {name} - {message}"
+
+* asctime - Log message timestamp consisting of date and time (with ms) separated by a space
+* levelname - Log level of the message
+* name - Logger name
+* message - Body of the log message
+
+This produces log messages such as this:
+
+    2022-04-29 10:38:52,315 [INFO] pyspam-app - Slicing 27 cans of spam into 6 slices each for a total of 162 slices.
+
+Basic Usage
+-----------
+For command line tools, after creating your parser with `argparse`, pass it to `add_logging_args()`. Then, after parsing
+arguments but before any logging, call `configure_logging_from_args(args.verbose, args.quiet, args.log_stdout)`:
+
+    import argparse
+    import logsetup
+
+    parser = argparse.ArgumentParser()
+
+    ... build your parser ...
+
+    logsetup.add_logging_args(parser)
+    args = parser.parse_args()
+    logsetup.configure_logging_from_args(args.verbose, args.quiet, args.log_stdout)
+
+This will set logging levels as requested by the command line options, with known external modules that would otherwise
+flood the logs to be set slightly less verbose. The specific list is in `logsetup.SPAMMY_LOGGERS` and can be
+edited before calling any configure logging function.
+
+The default log levels in `logsetup.DEFAULT_LOG_LEVEL` and `logsetup.DEFAULT_SPAMMY_LOG_LEVEL` can also be modified, if
+desired. These do not support custom logging levels, however.
+
+You may also pass a `logger_name` as a fourth argument to `configure_logging_from_args()` if you don't want to use the root
+logger. However, if your code is the main execution thread, you should generally configure the root logger so that all output
+uses the same log format.
+
+Finally, you can also call `configure_logging()` with specific log levels directly if needed.
+
+Once configured, each module or scripts should generate log messages with the default logger for their name:
+
+    import logging
+    LOG = logging.getLogger(__name__)
+
+Then just write to the log using that logger:
+
+    LOG.debug('This is a debug level log message.')
+    LOG.info('This is an info level log message.')
+    LOG.warning('This is a warning level log message.')
+    LOG.error('This is an error level log message.')
+    LOG.critical('This is a critical level log message.')
+
+Design Overview
+---------------
+The core assumptions are that logging should be easy to setup with reasonable defaults, configurable with command line options
+at runtime, and allow fine control over the volume of information output.
+
+To support this last point, there are modules that are commonly used and provide useful log information, but are also verbose
+when set to more detailed log levels despite usually not being the log messages you are interested in. The requests module is a
+great example of this. Debug level logs are verbose and produce tons of information, but the code itself is rarely the source
+of issues. Setting a general log level of debug means seeing both the debug messages of the problematic code and modules like
+requests, which just adds more messages to wade through that aren't helpful.
+
+Because of this, logsetup has a list of loggers which are known to be both reliable and noisy. When requesting more verbose
+log information, these "spammy" loggers trail behind the general log level by two steps. This causes more relevant logs to be
+displayed without the spammy logger information unless even more verbosity is requested.
+
+In practice, with the default settings, it results in the following level of log output per verbose flag given:
+
+| Verbosity | General Log Level | Spammy Logger Level |
+|-----------|:-----------------:|:-------------------:|
+| (none)    |      WARNING      |       WARNING       |
+| `-v`      |       INFO        |       WARNING       |
+| `-vv`     |       DEBUG       |       WARNING       |
+| `-vvv`    |       DEBUG       |        INFO         |
+| `-vvvv`   |       DEBUG       |        DEBUG        |
+
+Configuration
+-------------
+The default log levels in `logsetup.DEFAULT_LOG_LEVEL` and `logsetup.DEFAULT_SPAMMY_LOG_LEVEL` are set to
+WARNING and can be modified, if desired. Custom logging levels, however, are not supported.
+
+The set of loggers considered spammy is an iterable in `logsetup.SPAMMY_LOGGERS` and can also be modified or replaced.
+
+Finally, while not recommended, the log format can be modified by changing the value in `logsetup._LOG_FORMAT`. This
+uses the curly brace style formatting. Note this specific attribute is internal may undergo breaking changes in the future.
+The default format is: `"{asctime} [{levelname}] {name} - {message}"`
+
+All configuration changes should be made before calling any configuration functions.
+
+Function Overview
+-----------------
+For full details please see the source code and function documentation strings.
+
+### `add_logging_args(parser: argparse.ArgumentParser)`
+
+Adds the `--verbose`, `--quiet`, and `--log-stdout` options to the given argument parser. These arguments are used by
+`configure_logging_from_args()`.
+
+### `configure_logging_from_args(verbose: int = 0, quiet: int = 0, log_stdout: bool = False, logger_name: str = None)`
+
+Configures the specified logger, typically the root logger, from the given number of verbose and quiet flags, and, when
+increaing verbosity, sets the log level for known spammy loggers to trail behind by two log levels.
+
+### `configure_logging(log_level: int = None, spammy_log_level: int = None, log_stdout: bool = False, logger_name: str = None)`
+
+For the given logger, typically the root logger, overwrites the existing configuration to use the specified level and 
+standard format. Also sets the spammy loggers to their specified level. This function is used by
+`configure_logging_from_args()` and can alternately be called directly if needed.
+

loggery-0.3.1/README.md

@@ -0,0 +1,118 @@
+logsetup
+========
+*Easy and standardized logging for Python*
+
+Log Format
+----------
+This package configures logging with the following format:
+
+    "{asctime} [{levelname}] {name} - {message}"
+
+* asctime - Log message timestamp consisting of date and time (with ms) separated by a space
+* levelname - Log level of the message
+* name - Logger name
+* message - Body of the log message
+
+This produces log messages such as this:
+
+    2022-04-29 10:38:52,315 [INFO] pyspam-app - Slicing 27 cans of spam into 6 slices each for a total of 162 slices.
+
+Basic Usage
+-----------
+For command line tools, after creating your parser with `argparse`, pass it to `add_logging_args()`. Then, after parsing
+arguments but before any logging, call `configure_logging_from_args(args.verbose, args.quiet, args.log_stdout)`:
+
+    import argparse
+    import logsetup
+
+    parser = argparse.ArgumentParser()
+
+    ... build your parser ...
+
+    logsetup.add_logging_args(parser)
+    args = parser.parse_args()
+    logsetup.configure_logging_from_args(args.verbose, args.quiet, args.log_stdout)
+
+This will set logging levels as requested by the command line options, with known external modules that would otherwise
+flood the logs to be set slightly less verbose. The specific list is in `logsetup.SPAMMY_LOGGERS` and can be
+edited before calling any configure logging function.
+
+The default log levels in `logsetup.DEFAULT_LOG_LEVEL` and `logsetup.DEFAULT_SPAMMY_LOG_LEVEL` can also be modified, if
+desired. These do not support custom logging levels, however.
+
+You may also pass a `logger_name` as a fourth argument to `configure_logging_from_args()` if you don't want to use the root
+logger. However, if your code is the main execution thread, you should generally configure the root logger so that all output
+uses the same log format.
+
+Finally, you can also call `configure_logging()` with specific log levels directly if needed.
+
+Once configured, each module or scripts should generate log messages with the default logger for their name:
+
+    import logging
+    LOG = logging.getLogger(__name__)
+
+Then just write to the log using that logger:
+
+    LOG.debug('This is a debug level log message.')
+    LOG.info('This is an info level log message.')
+    LOG.warning('This is a warning level log message.')
+    LOG.error('This is an error level log message.')
+    LOG.critical('This is a critical level log message.')
+
+Design Overview
+---------------
+The core assumptions are that logging should be easy to setup with reasonable defaults, configurable with command line options
+at runtime, and allow fine control over the volume of information output.
+
+To support this last point, there are modules that are commonly used and provide useful log information, but are also verbose
+when set to more detailed log levels despite usually not being the log messages you are interested in. The requests module is a
+great example of this. Debug level logs are verbose and produce tons of information, but the code itself is rarely the source
+of issues. Setting a general log level of debug means seeing both the debug messages of the problematic code and modules like
+requests, which just adds more messages to wade through that aren't helpful.
+
+Because of this, logsetup has a list of loggers which are known to be both reliable and noisy. When requesting more verbose
+log information, these "spammy" loggers trail behind the general log level by two steps. This causes more relevant logs to be
+displayed without the spammy logger information unless even more verbosity is requested.
+
+In practice, with the default settings, it results in the following level of log output per verbose flag given:
+
+| Verbosity | General Log Level | Spammy Logger Level |
+|-----------|:-----------------:|:-------------------:|
+| (none)    |      WARNING      |       WARNING       |
+| `-v`      |       INFO        |       WARNING       |
+| `-vv`     |       DEBUG       |       WARNING       |
+| `-vvv`    |       DEBUG       |        INFO         |
+| `-vvvv`   |       DEBUG       |        DEBUG        |
+
+Configuration
+-------------
+The default log levels in `logsetup.DEFAULT_LOG_LEVEL` and `logsetup.DEFAULT_SPAMMY_LOG_LEVEL` are set to
+WARNING and can be modified, if desired. Custom logging levels, however, are not supported.
+
+The set of loggers considered spammy is an iterable in `logsetup.SPAMMY_LOGGERS` and can also be modified or replaced.
+
+Finally, while not recommended, the log format can be modified by changing the value in `logsetup._LOG_FORMAT`. This
+uses the curly brace style formatting. Note this specific attribute is internal may undergo breaking changes in the future.
+The default format is: `"{asctime} [{levelname}] {name} - {message}"`
+
+All configuration changes should be made before calling any configuration functions.
+
+Function Overview
+-----------------
+For full details please see the source code and function documentation strings.
+
+### `add_logging_args(parser: argparse.ArgumentParser)`
+
+Adds the `--verbose`, `--quiet`, and `--log-stdout` options to the given argument parser. These arguments are used by
+`configure_logging_from_args()`.
+
+### `configure_logging_from_args(verbose: int = 0, quiet: int = 0, log_stdout: bool = False, logger_name: str = None)`
+
+Configures the specified logger, typically the root logger, from the given number of verbose and quiet flags, and, when
+increaing verbosity, sets the log level for known spammy loggers to trail behind by two log levels.
+
+### `configure_logging(log_level: int = None, spammy_log_level: int = None, log_stdout: bool = False, logger_name: str = None)`
+
+For the given logger, typically the root logger, overwrites the existing configuration to use the specified level and 
+standard format. Also sets the spammy loggers to their specified level. This function is used by
+`configure_logging_from_args()` and can alternately be called directly if needed.

loggery-0.3.1/pyproject.toml

@@ -0,0 +1,46 @@
+[project]
+name = "loggery"
+version = "0.3.1"
+description = "Configure logging with reduced noise from spammy modules with easy argparse support"
+authors = [
+    {name = "Erskin Cherry", email = "erskin@eldritch.org"}
+]
+readme = "README.md"
+requires-python = ">=3.13"
+dependencies = [
+]
+classifiers = [
+    "Programming Language :: Python :: 3",
+    "Operating System :: OS Independent",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: GNU Lesser General Public License v3 or later (LGPLv3+)",
+]
+license = "LGPL-3.0-or-later"
+license-files = ["LICENSE"]
+[project.urls]
+Homepage = "https://gitlab.com/frobnic8/loggery"
+Repository = "https://gitlab.com/frobnic8/loggery"
+
+[tool.poetry]
+packages = [{include = "loggery", from = "src"}]
+
+
+[tool.poetry.group.dev.dependencies]
+pytest-mock = "^3.14.0"
+
+[build-system]
+requires = ["poetry-core>=2.0.0,<3.0.0"]
+build-backend = "poetry.core.masonry.api"
+
+[tool.pylint]
+max-line-length = 100
+
+[tool.pytest.ini_options]
+pythonpath = [
+  "src"
+]
+
+
+[tool.mypy]
+mypy_path = "src/:tests/"
+files = ["src/", "tests/"]

loggery-0.3.1/src/loggery/__init__.py

@@ -0,0 +1,187 @@
+"""loggery - Easy and standardized logging for Python
+
+For command line tools, after creating your parser with `argparse`, pass it to `add_logging_args()`.
+Then, after parsing arguments but before any logging, call
+`configure_logging_from_args(args.verbose, args.quiet, args.log_stdout)`:
+
+    import argparse
+    import loggery
+
+    parser = argparse.ArgumentParser()
+
+    ... build your parser ...
+
+    loggery.add_logging_args(parser)
+    args = parser.parse_args()
+    loggery.configure_logging_from_args(args.verbose, args.quiet, args.log_stdout)
+
+This will set logging levels as requested by the command line options, with known external modules
+that would otherwise flood the logs to be set slightly less verbose. The specific list is in
+`loggery.SPAMMY_LOGGERS` and can be edited before calling any configure logging function.
+
+The default log levels in `loggery.DEFAULT_LOG_LEVEL` and `loggery.DEFAULT_SPAMMY_LOG_LEVEL` can
+also be modified, if desired. These do not support custom logging levels, however.
+
+You may also pass a `logger_name` as a fourth argument to `configure_logging_from_args()` if you
+don't want to use the root logger.
+
+Finally, you can also call `configure_logging()` with specific log levels directly if needed.
+
+Once configured, each module or scripts should generate log messages with the default logger for
+their name:
+
+    import logging
+    LOG = logging.getLogger(__name__)
+
+Then just write to the log using that logger:
+
+    LOG.debug('This is a debug level log message.')
+    LOG.info('This is an info level log message.')
+    LOG.warning('This is a warning level log message.')
+    LOG.error('This is an error level log message.')
+    LOG.critical('This is a critical level log message.')
+"""
+
+import sys
+import argparse
+import importlib.metadata
+import logging
+
+__version__ = importlib.metadata.version("loggery")
+__author__ = "erskin@eldritch.org"
+
+# A set of loggers which we generally DON'T want to be quite as verbose as our main logger.
+# By default, if we are being more verbose, these are set to one log level less verbose than the
+# main log. If needed, you can add or remove items from this list before calling and configure
+# logging function.
+SPAMMY_LOGGERS = [
+    "google.auth.transport.requests",
+    "urllib3.util.retry",
+    "boxsdk.auth.oauth2",
+    "boxsdk.network.default_network",
+    "urllib3.connectionpool",
+    "gql.transport.requests",
+    "requests",
+]
+
+DEFAULT_LOG_LEVEL = logging.WARNING
+DEFAULT_SPAMMY_LOG_LEVEL = logging.WARNING
+
+_LOG_LEVELS = [
+    logging.CRITICAL,
+    logging.ERROR,
+    logging.WARNING,
+    logging.INFO,
+    logging.DEBUG,
+]
+
+_LOG_FORMAT = "{asctime} [{levelname}] {name} - {message}"
+
+
+def add_logging_args(parser: argparse.ArgumentParser):
+    """Add --verbose, --quiet, --log-stdout arguments to the given argument parser."""
+
+    parser.add_argument(
+        "-v",
+        "--verbose",
+        action="count",
+        default=0,
+        help=(
+            "increase level of feedback output. Use -vv for even more detail. Log level defaults "
+            "to " + repr(logging.getLevelName(DEFAULT_LOG_LEVEL))
+        ),
+    )
+    parser.add_argument(
+        "-q",
+        "--quiet",
+        action="count",
+        default=0,
+        help="decrease level of feedback output. Use -qq for even less detail",
+    )
+    parser.add_argument(
+        "--log-stdout",
+        action="store_true",
+        help="direct all logging to standard out instead of standard error",
+    )
+
+
+def configure_logging_from_args(
+    verbose: int = 0, quiet: int = 0, log_stdout: bool = False, logger_name: str | None = None
+):
+    """Configure logging based on the number of verbose and quiet flags and the log_stdout flag
+    added by add_logging_args().
+
+    Spammy loggers are those which, at more verbose log levels, are usually more noisy than useful.
+
+    Known spammy loggers in `loggery.SPAMMY_LOGGERS` are set up to two levels less verbose than
+    the main logger, but only when we are increasing the default verbosity.
+
+    With the standard defaults, this means that as verbosity goes up, the main logger will go from
+    WARNING to INFO, then DEBUG, and only then will the spammy loggers be set INFO, and then DEBUG.
+    But, as verbosity goes down, both the main and spammy loggers will be set to ERROR, and then
+    CRITICAL together.
+    """
+
+    # Set the log verbosity to the default, plus the count of verbose flags minus the count of
+    # quiet flags.
+    default_index = _LOG_LEVELS.index(DEFAULT_LOG_LEVEL)
+    verbosity = default_index + verbose - quiet
+
+    # Set the spammy loggers to track the verbosity of the main loggers to start.
+    spammy_verbosity = verbosity
+    if verbosity > default_index:
+        # But if we are being more verbose than normal, keep the spammy loggers quieter than the
+        # main ones, though never more quiet than the default spammy level.
+        default_spammy_index = _LOG_LEVELS.index(DEFAULT_SPAMMY_LOG_LEVEL)
+        spammy_verbosity = max(verbosity - 2, default_spammy_index)
+
+    # Cap the verbosity and spammy verbosity to indexes of LOG_LEVELS.
+    verbosity = min(verbosity, len(_LOG_LEVELS) - 1)
+    verbosity = max(verbosity, 0)
+    spammy_verbosity = min(spammy_verbosity, len(_LOG_LEVELS) - 1)
+    spammy_verbosity = max(spammy_verbosity, 0)
+
+    configure_logging(
+        _LOG_LEVELS[verbosity], _LOG_LEVELS[spammy_verbosity], log_stdout, logger_name
+    )
+
+
+def configure_logging(
+    log_level: int | None = None,
+    spammy_log_level: int | None = None,
+    log_stdout: bool = False,
+    logger_name: str | None = None,
+):
+    """Setup the specified logger to the given level and the standard format, and the level of
+    known spammy loggers.
+
+    This will remove any existing log handlers.
+    """
+
+    if not log_level:
+        log_level = DEFAULT_LOG_LEVEL
+
+    if not spammy_log_level:
+        spammy_log_level = DEFAULT_SPAMMY_LOG_LEVEL
+
+    logger = logging.getLogger(logger_name)
+    logger.setLevel(log_level)
+
+    # Remove any existing handlers so we overwrite the configuration.
+    for handler in logger.handlers[:]:
+        logger.removeHandler(handler)
+        handler.close()
+
+    # Setup the message handler and formatter.
+    stream = sys.stdout if log_stdout else sys.stderr
+    handler = logging.StreamHandler(stream)
+    handler.setLevel(log_level)
+    formatter = logging.Formatter(_LOG_FORMAT, style="{")
+    handler.setFormatter(formatter)
+
+    # Add the handler to the logger.
+    logger.addHandler(handler)
+
+    # Set the known spammy loggers to the request log level.
+    for spammy_logger_name in SPAMMY_LOGGERS:
+        logging.getLogger(spammy_logger_name).setLevel(spammy_log_level)