Virtualenv 20.23.1 fails to seed Python 3.12.0b3 leading to missing setuptools/wheel and failures about virtualenv HOT 5 CLOSED

https://virtualenv.pypa.io/en/latest/changelog.html#features-20-23-0 This is on purpose. Shouldn't assume that build tools are installed out of the box, you should specify your dependencies via the pep-518 that is widely available now for the last 5 years.

from virtualenv.

Pip builds packages in an isolated environment (where it installs setuptools if needed) by default. So there's no need for setuptools to be installed in the user's environment.

from virtualenv.

Pip builds packages in an isolated environment (where it installs setuptools if needed) by default. So there's no need for setuptools to be installed in the user's environment.

Then it's a bug in PIP because apparently that doesn't happen.

from virtualenv.

What makes you think it doesn't happen - you can't see the build environment directly, so how do you know pip didn't install setuptools?

If you have a reproducible example, and want to claim it's a pip bug, you should report it on the pip tracker.

from virtualenv.

What makes you think it doesn't happen - you can't see the build environment directly, so how do you know pip didn't install setuptools?

I can and this: https://github.com/pybuilder/pybuilder/actions/runs/5465477106/jobs/9948970088#step:3:1423

from virtualenv.