Timothée Mazzucotelli

OK, thanks for your answer. I'll try to play with REUSE in the next few weeks, and come up with a decision for this template :slightly_smiling_face: !

I don't use swap so it would be cool if we were also able to display/hide the swap part.

Thanks @romesco! Your workaround well, worked :smile: Here's my diff: ```diff [coverage:run] branch = true parallel = true source = - src/ + src/mkdocstrings/handlers/ tests/ ``` I had to specify...

Is there a way to see the exact file paths coveragepy finds and measures?

It's not odd at all in fact! These leading spaces are very important to distinguish between continuation lines of the current item, and the next item or block 🙂

Indeed, I managed to get a 65.91% coverage on this snippet with a Bash solution, using regular expressions and hacks, but without a lexer it will be impossible to get...

More info on [this stackoverflow post](https://stackoverflow.com/questions/6360929/bash-bug-re-lineno-or-am-i-just-confused) and in [this gist I made](https://gist.github.com/pawamoy/cca35f0f5ccd56665d6421e9b2d2d4bc) in response.

Just adding my testimony: I'm trying to use Bashcov in CI (Bash images, based on Alpine). ```yaml my-job: image: bash:5.0 before_script: - apk add --no-cache file ruby ruby-dev gcc libc-dev...

It would also help to improve contents at https://github.com/pawamoy/best-of-mkdocs :slightly_smiling_face:

I would personally prefer to use docstrings rather than comments for class variables or instance attributes documentation. This is what docstrings are used for.