** Description changed: [Impact] - * The pep517 module vendored in pip is missing its toml dependency. - This is used to ... - * An explanation of the effects of the bug on users and - justification for backporting the fix to the stable release. - * This upload backports upstream's 20.1 patch, replacing pytoml with - toml, following pep517. + * The pep517 module vendored in pip is missing its toml dependency. + * No specific examples of what that breaks, but it seems worth fixing + while we deal with LP: #1912248. + * This upload backports upstream's 20.1 patch, replacing pytoml with + toml, following pep517. [Test Case] # apt install python3 virtualenv - # virtualenv -p python3 foo + # virtualenv -p python3 foo # foo/bin/python -m pep517.build Note: ModuleNotFoundError: No module named 'toml' Ideally the virtualenv wouldn't even contain pep517, it would be internal to pip. See LP: #1904945 [Where problems could occur] - * Anybody who was expecting pytoml to be installed in Ubuntu Focal - virtualenvs will have their expectation broken. - They really shouldn't be expecting that, though. - + * Anybody who was expecting pytoml to be installed in Ubuntu Focal + virtualenvs will have their expectation broken. + They really shouldn't be expecting that, though. + [Original Bug Report] 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
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880749 Title: Ubuntu 20.04: virtualenv: pep517 requires toml, but it isn't bundled in venvs To manage notifications about this bug go to: https://bugs.launchpad.net/virtualenv/+bug/1880749/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
