Response inline below. On Mon, Jun 6, 2022 at 4:48 PM <c.bu...@posteo.jp> wrote:
> Dear Ian, > > thanks for the feedback. > > Am 06.06.2022 22:25 schrieb Ian Stapleton Cordasco: > [snip] What is against PEP8 checking via unittest? > > >From my perspective, I see them as two different tools. For example, I run pytest for unit tests, black for styling, mypy for typing, isort for sorting imports, etc. for each commit. > I am also aware of pre-commit framework. But it is to much and to > complex and yet another tool in the chain increasing the config error > risk. My projects currently are to small to invest in something like > this. > > I've not used pre-commit so I can't comment on it exactly. In most of my projects, I have either a Makefile or a shell script to abstract away all of the individual tools behind a single thing that I can call. So instead of running unit tests I run `make tests` or `./runtests.sh` to run my unit tests and the rest of my tooling. I don't see that as a big hurdle or significantly complicating my own tool chain. How do you currently run your unit tests? -- david stanek web: https://dstanek.com twitter: https://twitter.com/dstanek linkedin: https://www.linkedin.com/in/dstanek/
_______________________________________________ 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
