This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients brett.cannon, jaysinh.shukla, ncoghlan, nedbat
Date 2017-04-06.09:26:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1491470761.91.0.557073284246.issue11978@psf.upfronthosting.co.za>
In-reply-to
Content
As a starting point, I'd suggest looking at what can be achieved without making any changes to CPython or its test suite:

1. Set COVERAGE_PROCESS_START in the environment where the tests are being run

2. Inject a sitecustomize.py file into Lib (and add `Lib/sitecustomize.py` to `.gitignore`)

There are cases that won't cover (like subprocesses with a custom environment), but it will provide a starting point for the tests that just pass the current environment through, and will also provide a way to notify test.support.script_helper of the expected value of COVERAGE_PROCESS_START in the future.
History
Date User Action Args
2017-04-06 09:26:01ncoghlansetrecipients: + ncoghlan, brett.cannon, nedbat, jaysinh.shukla
2017-04-06 09:26:01ncoghlansetmessageid: <1491470761.91.0.557073284246.issue11978@psf.upfronthosting.co.za>
2017-04-06 09:26:01ncoghlanlinkissue11978 messages
2017-04-06 09:26:01ncoghlancreate