Logging setup in browser.py clobbers other logging
See original GitHub issueThe logging in browser.py calls the root logger, which can cause unexpected changes to the setup and output in some testing environments. It would be preferable to have it log to something like:
LOG = logging.getLogger(__name__)
...
except ImportError as e:
LOG.debug(f"Import warning: {e}")
Issue Analytics
- State:
- Created a year ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
A Complete Guide to Logging in Python with Loguru
Learn how to install, configure, and use the Loguru framework for logging in Python applications.
Read more >Logging HOWTO — Python 3.11.1 documentation
Basic Logging Tutorial: Logging is a means of tracking events that happen when some software runs. ... Another common way is to write...
Read more >A Step-by-Step Guide to Python Logging - Pylenin
In this article, you will learn about python logging module for logging events and why ... Logging messages to file using FileHandler method...
Read more >Logging in Python - Real Python
Logging is a very useful tool in a programmer's toolbox. It can help you develop a better understanding of the flow of a...
Read more >Python Logging Guide - Best Practices and Hands-on Examples
Line 1: import the logging module. Line 2: create a basicConf function and pass some arguments to create the log file. In this...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@fsouza @jsfehler thanks so much for everything!
Sent #1061. I haven’t bumped the version in a while, so opened as a PR.