On Wed, May 12, 2021 at 5:49 AM Eli Simhayev <eli.simha...@beyondminds.ai> wrote:
> Hi, > > > > Firstly, thank you for the awesome work. > > Currently I’m using pre-commit with black, isort and another small hooks. > > > > What the preferable way to integrate pylint (in terms of workflow) in my > use-case? > It's unclear what your workflow is currently such that it doesn't seem like a recommendation could be made. For example, I could assume you use vim and either coc.vim or vim-ale and would suggest you add pylint as a linter for Python files to the configuration for either of those plugins. That would give you in-the-moment warnings while adding it to pre-commit to ensure you didn't miss something. But I don't know what your actual workflow is beyond the fact you use pre-commit and pylint can be easily added to that (to the best of my knowledge).
_______________________________________________ code-quality mailing list -- code-quality@python.org To unsubscribe send an email to code-quality-le...@python.org https://mail.python.org/mailman3/lists/code-quality.python.org/ Member address: arch...@mail-archive.com
