0.14.0 no longer runs pylint if invoked via --pylint -m pylint

[pjz]

I wondered why my test suite failed and it was because my pylint checking - done with something like:

pytest --pylint -m pylint mymodule

ends up "collecting 0 items" to check.

Works fine with 0.13.0.

[carsongee]

This is actually the primary feature of 0.14.0. We cache the test results of pylint unless the file has changed to optimize runtime. So for example, if you run pytest --pylint -m pylint mymodule --cache-clear you should see those tests run. Also, if you change one file, you should see that collection number got to 1

[chaoflow]

@carsongee It seems that at least for me something is going wrong (regarding caching) with 0.14.0 and 0.14.1. They do not run any linting, whereas 0.13.0 still does.

$ pytest --pylint -m pylint --cache-clear
platform linux -- Python 3.7.3, pytest-5.0.1, py-1.8.0, pluggy-0.12.0
...
plugins: cov-2.7.1, flake8-1.0.4, forked-1.0.2, mock-1.10.4, xdist-1.29.0, pylint-0.14.1
collected 49 items / 49 deselected

$ pytest --pylint -m pylint --cache-clear
platform linux -- Python 3.7.3, pytest-5.0.1, py-1.8.0, pluggy-0.12.0
...
plugins: cov-2.7.1, flake8-1.0.4, forked-1.0.2, mock-1.10.4, xdist-1.29.0, pylint-0.13.0
collected 157 items / 49 deselected / 108 selected