ablatner

I see this error as well with a GH runner and setup-python@v5. ``` Current runner version: '2.313.0' Runner name: 'ubuntu-64-core_52f54d836f2b' ``` ``` - name: Set up python uses: actions/setup-python@v5 env:...

I'm able to work around this with the expected pip command: ``` - name: Install setuptools shell: cmd run: py -m pip install --upgrade pip setuptools wheel ```

This seems to reproduce it: https://github.com/ablatner/windows-runner-test/pull/1 It calls setup-python with 3.9.13 and then runs a script that imports `setuptools.extern`. Note that this uses `windows-latest` instead of `windows-latest-8-core` because it's not...

As in my org's private repo, this works after manually installing setuptools with pip: https://github.com/ablatner/windows-runner-test/pull/2

@dmitry-shibanov this is still an issue, demonstrated by my [test PR](https://github.com/ablatner/windows-runner-test/pull/1).

My project's constraint autoupdater is affected by this. After bumping setuptools to 69.0.3, subsequent updates with `pip list -e` don't recognize editable installs with underscores. For now, we can pin...

I had pinned my project to setuptools 69.0.2 until pip was updated to 24.0. I updated setuptools to 69.1.0, and the next constraint update broke my editable installs in the...

@jaraco @sbidoul do you have any thoughts?

Unfortunately it is in a private corporate repository. Maybe to take a step back, should we expect a difference in package names for the command `python3 -m pip list -e`,...