Is there a problem with the generated directory

[zhijian-pro]

python3.10 -m virtualenv vvv

cd vvv
tree -L 5
.
├── lib
│   └── python3.10
├── pyvenv.cfg
└── usr
    └── local
        ├── bin
        │   ├── activate
        │   ├── activate.csh
        │   ├── activate.fish
        │   ├── activate.nu
        │   ├── activate.ps1
        │   ├── activate_this.py
        │   ├── deactivate.nu
        │   ├── pip
        │   ├── pip-3.10
        │   ├── pip3
        │   ├── pip3.10
        │   ├── python -> /usr/local/opt/python@3.10/bin/python3.10
        │   ├── python3 -> python
        │   ├── python3.10 -> python
        │   ├── wheel
        │   ├── wheel-3.10
        │   ├── wheel3
        │   └── wheel3.10
        └── lib
            └── python3.10
                └── site-packages

8 directories, 19 files

Is there a problem with the generated directory ?
Is it normal to have no vvv/bin directory？
some context: pre-commit/pre-commit#2270

[gaborbernat]

It's normal if your OS has oddly configured Python. Can you post the output of python3.10 -m virtualenv vvv -vvvv?

Edit: I believe this bug has been fixed a while back, please upgrade your virtualenv to pypi.org/project/virtualenv/20.13.3

[zhijian-pro]

it that ok ?

[gaborbernat]

Run virtualenv --reset-app-data vvv -vvvv --without-pip --clear and check again 😊 I think after you should be ok.

[zhijian-pro]

yes! thanks !
pre-commit can be used normally, what is the reason? Is it a bug?

[gaborbernat]

A bit. virtualenv 20.0.35 is ancient and did not support homebrew python correctly. This was fixed in a later version but seems virtualenv 20.0.35 created a broken python information file that poisoned newer versions too. Hence why resetting the application data fixed it. I don't think there's anything to do on our side, other than who run into it to update to the latest virtualenv and run once virtualenv --reset-app-data vvv -vvvv --without-pip --clear to reset their application data.

[zhijian-pro]

Thanks !

[gaborbernat]

This issue was caused by corrupted virtualenv cache data that persisted incorrect Python metadata. The solution is to run virtualenv --reset-app-data which clears the cached py_info JSON files and resolves the incorrect directory structure issue. Closing as answered.