You will notice there are a plethora of extra packages in the virtual environment that should not normally be there, resulting in a dirty virtual environment.
To make matters worse, the latest release of pip bundles incompatible versions of libraries. The net result is that `pip install pep517` will show that it is already installed, and but `import pep517` will result in an ImportError.
This problem has been fixed in the Debian Testing/Unstable python-virtualenv package. Could the Ubuntu package backport these fixes?
On a clean 20.04 machine (or container), observe the following:
apt-get update
apt-get install -y python3-virtualenv
python3 -m virtualenv foo && source foo/bin/activate
pip list
You will notice there are a plethora of extra packages in the virtual environment that should not normally be there, resulting in a dirty virtual environment.
The packages listed here are those that are bundled with pip: https:/ /github. com/pypa/ pip/tree/ master/ src/pip/ _vendor
To make matters worse, the latest release of pip bundles incompatible versions of libraries. The net result is that `pip install pep517` will show that it is already installed, and but `import pep517` will result in an ImportError.
This problem has been fixed in the Debian Testing/Unstable python-virtualenv package. Could the Ubuntu package backport these fixes?
This is blocking Ansible supporting 20.04 officially, since the dirty virtualenvs are causing our tests to fail. https:/ /github. com/ansible/ ansible/ issues/ 69203