-j doesn’t offer any benefit but does create some pain, it doesn’t even make runs faster. It should just be removed/disabled/pass-thru’d, for now, until it’s stable and does what it says on the tin.

I’ve a few PRs aimed at testing the parallel aspect, improving the accuracy and eventually improving the performance of it.... but it’s been slow going getting them in, partly my fault, but partly because of the feedback cadence.

On Sun, 23 Aug 2020 at 14:55, David Resnick via code-quality <code-quality@python.org> wrote:

Thanks a lot for the idea, Florian.

Removing that flag has made a huge difference in my pylint runs. I don't know if it will stop it from being flaky, but after the flag was removed I received a lot of correct warnings that for some reason were not being shown. It is definitely a good idea not to use this flag.

- David

On Wed, Aug 12, 2020 at 11:38 PM Florian Bruhin <me@the-compiler.org> wrote:
Hey,

On Wed, Aug 12, 2020 at 09:12:00AM -0000, David Resnick via code-quality wrote:

> I thought that I'd ask here before opening an issue. I'm seeing intermittent

> warnings on the same code.

Perhaps a shot in the dark, but do you happen to use multiple jobs via pylint's

-j option? I've seen various funny behavior when doing that.

Florian

--

me@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org

https://bruhin.software/ | https://github.com/sponsors/The-Compiler/

GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc

I love long mails! | https://email.is-not-s.ms/

_______________________________________________

code-quality mailing list -- code-quality@python.org

To unsubscribe send an email to code-quality-leave@python.org

https://mail.python.org/mailman3/lists/code-quality.python.org/

Member address: frank@doublethefish.com