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 due to the toml issue).
As mentioned, we can work around this by installing toml. I'm more worried about the broader issue in the report, that virtualenvs are dirty in the first place, this limits their utility :(
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 due to the toml issue).
As mentioned, we can work around this by installing toml. I'm more worried about the broader issue in the report, that virtualenvs are dirty in the first place, this limits their utility :(