Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

python-no-log-warn catches valid methods

See original GitHub issue

The standard library package warning has a .warn() method. This check incorrectly blocks when that method is used.

The description states this is a “A quick check for the deprecated .warn() method of python loggers.”

As a user, I would expect this check to only check logger objects for usages of the .warn method. What I experience is that warnings.warn() is being flagged.

Issue Analytics

State:
Created 4 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

asottilecommented, Jul 24, 2019

pre-commit run --all-files 😉

0reactions

asottilecommented, Jul 24, 2019

via #18

Top Results From Across the Web

Style - Scikit-HEP

Flake8. Flake8 can check a collection of good practices for you, ranging from simple style to things that might confuse or detract users,...

Writing better Python code, automatically - mje.nz

Step 1: catching bugs and anti-patterns; Step 2: enforcing best practices; Step 3: maintaining a consistent style; Step 4: bonus points.

ignore doctests/docstrings with pyflakes/pylint - splunktool

When the IGNORE_EXCEPTION_DETAIL doctest option is specified, everything following the leftmost colon and any module information in the ...

idesolver [python]: Datasheet - Package Galaxy

... for all the input functions - Catch error for complex valued functions when y_0 is real, ... + informational: true ... +...

The pygrep-hooks from pre-commit - GithubHelp

python-no-log-warn catches valid methods. The standard library package warning has a .warn() method. This check incorrectly blocks when that method is used.