fix: can't use PYPYVERSION without checking PYPY first

nedbat · Oct 20, 2022 · 4668a92 · 4668a92
1 parent a3c8683
commit 4668a92
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 1 deletion.
diff --git a/CHANGES.rst b/CHANGES.rst
@@ -30,7 +30,11 @@ Unreleased
   - A ``[paths]`` setting like ``*/foo`` will now match ``foo/bar.py`` so that
     relative file paths can be combined more easily.
 
+- Fix internal logic that prevented coverage.py from running on implementations
+  other than CPython or PyPy (`issue 1474`_).
+
 .. _issue 991: https://github.com/nedbat/coveragepy/issues/991
+.. _issue 1474: https://github.com/nedbat/coveragepy/issues/1474
 
 
 .. _changes_6-5-0:

diff --git a/coverage/env.py b/coverage/env.py
@@ -85,7 +85,10 @@ class PYBEHAVIOR:
     nix_while_true = (PYVERSION >= (3, 8))
 
     # CPython 3.9a1 made sys.argv[0] and other reported files absolute paths.
-    report_absolute_files = ((CPYTHON or (PYPYVERSION >= (7, 3, 10))) and PYVERSION >= (3, 9))
+    report_absolute_files = (
+        (CPYTHON or (PYPY and PYPYVERSION >= (7, 3, 10)))
+        and PYVERSION >= (3, 9)
+    )
 
     # Lines after break/continue/return/raise are no longer compiled into the
     # bytecode.  They used to be marked as missing, now they aren't executable.