src-d/wmd-relax

Use different logging levels

Open

#17 opened on Jun 11, 2017

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Python (456 stars) (83 forks)batch import
enhancementhelp wanted

Description

At the moment everything is on info, might be good to change it so you can choose whether you want super granualar output or just the reasons why the nearest_neighbour method stopped.

Contributor guide

Tech stack
python
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Pythonlogging module
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Look at the current logging usage in the codebase, likely in files like `wmd.py` or `nearest neighbour.py`. The `nearest neighbour` method currently logs with `logging.info`. Introduce a configurable log level, perhaps via an argument to the main function or an environment variable. Ensure that only messages at or above the chosen level are output. The issue suggests allowing 'super granular output' vs. just reasons for stopping, so consider implementing DEBUG and INFO levels.
Use different logging levels · src-d/wmd-relax#17 | Good First Issue