[issue38393] building modules from 3.8.0rc1 fails in a venv when system 3.8 is present

STINNER Victor added the comment: The problem is that Python looks for pyvenv.cfg in the program directory or in its parent directory. For example: /tmp/testenv/Python-3.8.0rc1/python looks for /tmp/testenv/Python-3.8.0rc1/pyvenv.cfg (doesn't exist) and /tmp/testenv/Python-3.8.0rc1/pyvenv.c

[issue38393] building modules from 3.8.0rc1 fails in a venv when system 3.8 is present

Change by pmp-p : -- versions: +Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue38393] building modules from 3.8.0rc1 fails in a venv when system 3.8 is present

STINNER Victor added the comment: It's not a Python 3.8 regression. Python 3.7 has the same behavior. cd $HOME python3.7 -m venv testenv cd testenv/ . bin/activate wget https://www.python.org/ftp/python/3.8.0/Python-3.8.0rc1.tar.xz tar -xf Python-3.8.0rc1.tar.xz && cd Python-3.8.0rc1 CC=clan

[issue38393] building modules from 3.8.0rc1 fails in a venv when system 3.8 is present

New submission from pmp-p : when trying to build rc1 from a b4 venv to prepare a python host for cross compilation on ubuntu xenial flavour x64 i got : cd /tmp python3.7 -m venv testenv cd testenv/ . bin/activate (testenv) /tmp/testenv $ tar xf /tmp/Python-3.8.0rc1.tar.xz && cd Python-3.8.0