• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

MITLibraries / timdex-dataset-api / 12753346300

13 Jan 2025 06:04PM UTC coverage: 97.423%. First build
12753346300

push

github

ghukill
Simplify logging setup

Why these changes are being introduced:

As a library that is installed by other applications, it is beneficial to
have this library logging follow the levels and handlers set by the calling
context.  That said, it can also be helpful to set a level like INFO for the
calling context, but DEBUG for this library.

What we definitely want to avoid is this library setting up a handler and
outputting logs, only to have them duplicated in the calling context.

How this addresses that need:
* Remove setting up of handlers; rely on calling context for handlers

Side effects of this change:
* For local development logging statements will not show up without
some kind of manual logging.basicConfig() call or handler setup.
* For calling contexts Transmogrifier, pipeline lambdas, and TIM to show this
library's DEBUG logs, they will need to adjust their configure_logger() functions
to avoid filtering out loggers from different namespaces.

Relevant ticket(s):
* https://mitlibraries.atlassian.net/browse/TIMX-427

9 of 10 new or added lines in 2 files covered. (90.0%)

189 of 194 relevant lines covered (97.42%)

0.97 hits per line

Source File
Press 'n' to go to next uncovered line, 'b' for previous

90.91
/timdex_dataset_api/config.py


Source Not Available

STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc