#2311 pex3 venv create inconsistently creates a plain venv Issue created by zmanji This inconsistency is a minor issue but surprised me recently. Creating a venv via a requirement produces a plain venv

pex3 venv create  --force -d ./tenv --no-build 'mypy'
ls ./tenv 
bin        include    lib        pyvenv.cfg

Creating a pex of the requirement and then creating a venv from the pex repository produces a pex venv

pex --pip-version 23.2 --resolver-version pip-2020-resolver --no-build 'mypy' -o test.pex
pex3 venv create --force -d ./tenv  --no-build --pex-repository ./test.pex 'mypy'
ls ./tenv
PEX-INFO    __main__.py bin         include     lib         pex         pyvenv.cfg

I would expect both steps to be consistent but maybe I missed something in the documentation pantsbuild/pex