Skip to content

Consider adding environment variable when running #553

Closed
@nedbat

Description

@nedbat

Originally reported by Pedro Algarvio (Bitbucket: s0undt3ch, GitHub: s0undt3ch)


When checking coverage using "coverage run" consider injecting a COVERAGE_ environment variable.

This would allow detecting that the code is being covered and proceed acroding to that information.

For example, to speed up tests I often just kill any subprocesses spawned instead of terminating them(yes we spawn a lot of processes and it does make a huge difference), however, this results in the coverage data not being written.

Should I provide a PR?

Maybe COVERAGE_COMMAND, which in this case would be set to run?


Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions