> What is the impact of this? It seems to happily install PEP 517
packages as-is.
@Stefano sorry for the delay here. Installing PEP517 packages is fine
without the patch, but building them (building a wheel) is where the
issue comes in.
If you need a concrete example, download the .tar.gz of any
The impact of the pep517 issue isn't too big of an issue for us- we can
work around it (installing toml).
The "impact" is that we have a test scenario which runs `pip install
pep517` (reports already installed) and then tries to do `python -m
pep517.build --binary --out-dir dist .` (which fails du
Sorry, posted that from the wrong account, that comment was by me (the
original bug reporter).
--
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:
python3 virtualenvs include (broken) bundl
Public bug reported:
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 no
