summaryrefslogtreecommitdiff
path: root/metacov.ini
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2018-10-14 17:13:46 -0400
committerNed Batchelder <ned@nedbatchelder.com>2018-10-14 17:13:46 -0400
commit83ccf7ad923f75c736c42bf9117a57a156042c4a (patch)
treec11febaebbcebef54abcbdcd25285ff4a62178ba /metacov.ini
parent7a5e8a4fa39c9840e292120783b69566ac15f1e5 (diff)
downloadpython-coveragepy-git-83ccf7ad923f75c736c42bf9117a57a156042c4a.tar.gz
Have to rethink how to use contexts ourselves
Contexts fail when using PYTRACER, and we want to measure coverage under PYTRACER (at least for PyPy), so we need a more sophisticated strategy for how to use contexts.
Diffstat (limited to 'metacov.ini')
-rw-r--r--metacov.ini2
1 files changed, 0 insertions, 2 deletions
diff --git a/metacov.ini b/metacov.ini
index fc85f26e..80c508e9 100644
--- a/metacov.ini
+++ b/metacov.ini
@@ -9,8 +9,6 @@ parallel = true
source =
${COVERAGE_HOME?}/coverage
${COVERAGE_HOME?}/tests
-context = ${COVERAGE_PYVERSION?}
-dynamic_context = test_function
[report]
# We set a different pragma so our code won't be confused with test code.