For example in the commit https://github.com/pypa/virtualenv/commit/445a68dffa7ba5c0af3b02ec0545b760cd8c04ba it was fixed that the venv prefix on Debian systems with 3.10 includes a wrong "local" prefix. But since virtualenv caches the PythonInfo class on disk if it called with a specific executable (e.g. poetry specifies a specific exe), it can happen that broken information is provided for the virtual env creation.
The package should include a mechanism to invalidate the cache data if the internals of the PythonInfo changes.
Environment
Provide at least:
OS: Debian unstable
Python: 3.10.9
pip list of the host python where virtualenv is installed:
Issue
For example in the commit https://github.com/pypa/virtualenv/commit/445a68dffa7ba5c0af3b02ec0545b760cd8c04ba it was fixed that the venv prefix on Debian systems with 3.10 includes a wrong "local" prefix. But since
virtualenv
caches the PythonInfo class on disk if it called with a specific executable (e.g. poetry specifies a specific exe), it can happen that broken information is provided for the virtual env creation.The package should include a mechanism to invalidate the cache data if the internals of the PythonInfo changes.
Environment
Provide at least:
pip list
of the host python wherevirtualenv
is installed: