Have you asked elsewhere?

There are other good places to ask for help using coverage.py. These places let
other people suggest solutions, are more likely places for people to find your
question:

• Stack Overflow
• discuss.python.org

Describe your situation

Wherever you ask your question, be sure to explain:

• What you did
• What happened
• How that was different than what you wanted to happen
• What kind of help you need

My testing action (https://github.com/pylint-dev/pylint-pytest/actions/runs/20776501197) includes a lot of what-appears-to-be Python stdlib (e.g. / opt / homebrew / Cellar / python@3.13 / 3.13.11 / Frameworks / Python.framework / Versions / 3.13 / lib / python3.13 / _pyio.py), resulting into a whopping ~5 MB artifact (instead of the Windows / Linux of ~ 140 KB).

I have read the https://coverage.readthedocs.io/en/7.13.1/source.html#specifying-source-files - and I even include the paths.source configuration (https://github.com/pylint-dev/pylint-pytest/blob/ddd4b4a68b8fe646f40424851f2ca0ee6f53627b/pyproject.toml#L101-L103) but I am not sure what the problem is. Do I really need to switch to coverage run ...?

(PS: Also Linux one includes the  / etc / python3.12 / sitecustomize.py - but that's a very small thing compared to the MacOS size)

Searched: https://github.com/coveragepy/coveragepy/issues?q=sort%3Aupdated-desc%20is%3Aissue%20macos%20%2Fopt