happy-pizza-3050711/21/2021, 12:53 PM
. I notice that pants 2.9.0.dev2 uses pylint 2.11.0+, which supports
option for generating report file. I have that specified as
in pants.toml. I observe that the output isn't printed on the console but, after the run, I can't find the generated report anywhere under the project root. Maybe I forgot to check somewhere else?
[pylint].args = "--output=./pylint.report.txt"
curved-television-656811/21/2021, 6:18 PM
happy-kitchen-8948211/21/2021, 6:22 PM
, but it looks like we don't do that for pylint
an absolute path, so you can send that report anywhere...
happy-pizza-3050711/21/2021, 10:03 PM
. I'm getting the below output when running on osx. Not knowing the exact internals, I guess that the files in
are being monitored by pants and writing pylint report file right there invalidates the linting process in some way, causing a new job to be rescheduled (and to be invalidated again). Specifying the report under "dist" directory seems to be a better choice.
❯ ./pants lint :: 22:32:51.67 [INFO] Initializing scheduler... 22:32:51.81 [INFO] Scheduler initialized. 22:32:53.62 [INFO] Filesystem changed during run: retrying `Lint` in 500ms... 22:32:54.55 [INFO] Filesystem changed during run: retrying `Lint` in 500ms... ... Interrupted by user.
hundreds-father-40411/22/2021, 1:20 AM
, list the