Matthew Gamble

> No caching in Docker builds because source is required to install 3rd party dependencies I've been working around this by using `touch` to create a whole bunch of dummy...

> the other workaround I’ve seen/used is to use the poetry export plugin to export a text file for each subproject/dependency group then manipulate that text file to remove path...

@adriangb Yes, I believe that PR does solve my problems :) Thank you!

> The issue with the solution you proposed is that you never install the transitive 3rd party dependencies (which may even be all 3rd party dependencies if there is no...

> On the other hand, I wouldn't like to skip .github/workflows/*.yml. The same applies to `.buildkite/pipeline.yaml` for example. It's significantly easier to not have to worry about manually ensuring these...

Yes, it probably makes sense to only enable that behaviour by setting a flag.

Perhaps a better approach would be to create a `CheckOptions` class, and move the `verbose` parameter in there. Then you can add additional (optional) parameters to that class as desired,...

Given that issue has been open for three and a half years with no traction, I think support for JSON should be implemented in this plugin. What kind of overhead...

Turns out the implementation wasn't very complicated, so I went ahead and did it: https://github.com/pytest-dev/pytest-cov/pull/582 I appreciate the points made in #337, but I think the consensus there is that...

> Help me understand why running coverage json is difficult? - It's an additional step. Having pytest just generate the JSON file automatically is much more convenient, for the same...