fix: PyPy started making argv[0] absolute. Fixes #1426

Author: nedbat

CHANGES.rst

@@ -20,7 +20,11 @@ development at the same time, such as 4.5.x and 5.0.
 Unreleased
 ----------
 
-Nothing yet.
+- PyPy started reporting executed files as absolute.  Coverage.py adapted,
+  fixing `issue 1426`_.
+
+.. _issue 1426: https://github.com/nedbat/coveragepy/issues/1426
+
 
 
 .. _changes_6-4-2:

coverage/env.py

@@ -85,7 +85,7 @@ 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 and PYVERSION >= (3, 9))
+    report_absolute_files = ((CPYTHON or (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.

tests/test_process.py

@@ -302,8 +302,11 @@ def f2():
         status, out = self.run_command_status("coverage run throw.py")
         out2 = self.run_command("python throw.py")
         if env.PYPY:
-            # Pypy has an extra frame in the traceback for some reason
+            # PyPy has an extra frame in the traceback for some reason
             out2 = re_lines_text("toplevel", out2, match=False)
+            # It also uses full paths when making files absolute
+            if env.report_absolute_files:
+                out2 = re.sub(r'File "' + re.escape(os.getcwd()) + ".", 'File "', out2)
         assert out == out2
 
         # But also make sure that the output is what we expect.