python -m venv from within tox env fails with PyPy 7.3.16 on Windows #4958
Description
(I don't know whether this is tox's fault or PyPy's fault, so I'm reporting it in both places. Tox issue: tox-dev/tox#3284)
Given the following tox.ini:
[testenv]
skip_install = True
commands =
python script.pyand the following script.py:
import subprocess
import sys
subprocess.run([sys.executable, "-m", "venv", "venvdir"], check=True)Running tox on Windows (specifically, GitHub Actions' windows-latest runner) using PyPy 7.3.16 (whether as Python 3.9.19 or Python 3.10.14) fails with:
Error: problem finding exes in ['libffi-8.dll', 'libpypy3.10-c.dll', 'pypy.exe', 'pypy3.10.exe', 'pypy3.10w.exe', 'pypy3.exe', 'pypyw.exe', 'python.exe', 'python3.10.exe', 'python3.exe', 'pythonw.exe']
Traceback (most recent call last):
File "D:\a\test\test\script.py", line 4, in <module>
subprocess.run([sys.executable, "-m", "venv", "venvdir"], check=True)
File "C:\hostedtoolcache\windows\PyPy\3.10.14\x86\Lib\subprocess.py", line 526, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['D:\\a\\test\\test\\.tox\\py\\Scripts\\python.EXE', '-m', 'venv', 'venvdir']' returned non-zero exit status 1.
Running the script outside of tox works, as do running tox with PyPy 7.3.15 and running tox with PyPy 7.3.16 on Ubuntu or macOS.