Jason R. Coombs

After [working around a bug in act](https://github.com/nektos/act/issues/2220#issuecomment-2105011307), I've been able to replicate the failure reliably with the act command above. Moreover, by rolling back to an older docker image using...

I've bisected the config from the bottom up and only after re-adding the full metadata section does the problem go away. I'm not yet sure if it's related, but [this...

Investigating a bit more, I've put a breakpoint at the top of `/usr/lib/python3.10/_distutils_system_mod.py` and I've found that when running a build against main, that breakpoint is never hit, but in...

And the behavior on main seems like the right behavior - if SETUPTOOLS_USE_DISTUTILS=stdlib, then the _distutils_system_mod shouldn't be invoked. Using this dockerfile: ```Dockerfile FROM jaraco/multipy-tox:jammy RUN apt install -y vim...

I put a breakpoint in `setuptools._distutils` and confirmed that it's not imported at all during a full build under setup.cfg, so it's merely the fact that pyproject.toml requires extra evaluation...

> 1. We can change all uses of `orig.install` in `setuptools/command/install.py`'s methods to `super()`, so it does not attempt to resolve the `orig.install` binding and just get the right thing...

> > 1. We can change all uses of `orig.install` in `setuptools/command/install.py`'s methods to `super()`, so it does not attempt to resolve the `orig.install` binding and just get the right...

Looks like the tests now pass when targeting main after #4361.

> It's unfortunate that this affects any CLI tool that wants to be `my-package` versus `my_package` and builds with setup.py. I only expect the name of the package as reflected...

@hugovk Based on my description, do you want to advocate not to revert the changes?