Purpose of WITH_COVERAGE about cookiecutter-pylibrary HOT 5 CLOSED

On my second question, I'm starting to suspect that I may not be seeing the benefit because of how the projects I have coverage on are laid out.

from cookiecutter-pylibrary.

This env duplication is usually necessary in timing sensitive projects (as I have found out bugs in https://pypi.python.org/pypi/manhole or https://pypi.python.org/pypi/pytest-benchmark I wouldn't been able to find otherwise).

It's a good practice for complicated projects but as you can see the default options (test_matrix_separate_coverage=no) of this template make a project without the cover/nocov envs - it makes everything twice as slow 😁

from cookiecutter-pylibrary.

Awesome! thanks for the info.

I just realized my first question talks about a missing reference, but i never said what I was talking about. I had meant the WITH_COVERAGE env. variable.

from cookiecutter-pylibrary.

I forgot about it. Some support env var for subprocess setup for coverage that I used long time ago. No longer necessary now (pytest-cov already does it).

from cookiecutter-pylibrary.

Awesome. Thanks!

from cookiecutter-pylibrary.