search

pylint-dev / pylint-pytest

A Pylint plugin to suppress pytest-related false positives.
https://pypi.org/project/pylint-pytest/
MIT License
14 stars 3 forks source link

Weird recursion when upgrading from `pylint-pytest < 1.1.0` with `pylint` 2 to their latest versions #61

Closed webknjaz closed 2 months ago

webknjaz commented 2 months ago

Describe the bug

Here's what I'm doing: https://github.com/cherrypy/cheroot/commit/f109e854f7f2d7d750e557688316dfaace62c443#diff-63a9c44a44acf85fea213a857769990937107cf072831e1a26808cfde9d096b9L270

To Reproduce

See https://github.com/cherrypy/cheroot/pull/698. Getting the repo and running tox -e pre-commit -- pylint --all-files -vv

Expected behavior

If there's something wrong with the configuration, the error message should state that instead of spitting out tracebacks...

Additional context

I'm trying to upgrade some old linter pins to as new as I can. pylint is wrapped with pre-commit which runs on pre-commit.ci and the normal CI is also running it through tox.

webknjaz commented 2 months ago

Is this https://github.com/pylint-dev/pylint-pytest/issues/56? I'll try the suggestion to use an alpha release and report back.

webknjaz commented 2 months ago

Is this #56? I'll try the suggestion to use an alpha release and report back.

Yep, using pylint-pytest ~= 2.0.0a0 fixes it. I'll mark it as resolved and hopefully other people will be able to locate the closed issue when debugging...

stdedos commented 2 months ago

Duplicate of https://github.com/pylint-dev/pylint-pytest/issues/56

I have one pesky issue that I'd like to fix before v2 - and sadly I haven't "meaningfully" contributed time towards https://github.com/pylint-dev/pylint-pytest for (more than) a couple of months