You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See cherrypy/cheroot#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.
The text was updated successfully, but these errors were encountered:
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...
This version supports Python 3.12 officially. As a part of this patch,
`pylint-pytest` is also updated with the bugfixes needed to stop
capping it.
An alpha version of the plugin is used due to a bug when running
`pylint` in parallel mode [[1]].
[1]: pylint-dev/pylint-pytest#61
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
Describe the bug
Here's what I'm doing: cherrypy/cheroot@f109e85#diff-63a9c44a44acf85fea213a857769990937107cf072831e1a26808cfde9d096b9L270
To Reproduce
See cherrypy/cheroot#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.
The text was updated successfully, but these errors were encountered: