Pip install has different version in metadata: '20.8'

[jrdzha]

Installing black on Ubuntu, Python 3.8 results in the following error:

root@2971284e07e9:/# python3 -m pip install black
Collecting black
  Downloading black-20.8b1.tar.gz (1.1 MB)
     |████████████████████████████████| 1.1 MB 3.4 MB/s 
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
    Preparing wheel metadata ... done
ERROR: Requested black from https://files.pythonhosted.org/packages/dc/7b/5a6bbe89de849f28d7c109f5ea87b65afa5124ad615f3419e71beb29dc96/black-20.8b1.tar.gz#sha256=1c02557aa099101b9d21496f8a914e9ed2222ef70336404eeeac8edba836fbea has different version in metadata: '20.8'

To Reproduce Steps to reproduce the behavior:

1. Using Python3.8 in Ubuntu Docker image
2. Run python3 -m pip install black

Expected behavior The pip install should work

Environment (please complete the following information):

• Version: 20.8b1
• OS and Python version: Ubuntu/Python 3.8.7

[ofek]

We're also experiencing this in our CI DataDog/integrations-core#8378

[seanlaw]

Same here. This just started happening in the past 20 minutes on both Azure Pipelines and Github Actions.

Thank you for your time and attention.

[MohamedElgammal]

Same here with Github actions

[ticdenis]

Same here with Github actions too

[iot-resister]

Same with gitlab ci

[amanda-wee]

Confirmed with Github actions

[vint21h]

Same at localhost using pip and pipenv.

[ichard26]

TO EVERYONE IN THIS THREAD

Please make sure you have setuptools==51.3.1 (or higher?) installed (thanks #1933 (comment))

unimportant/outdated info (if you're a follow maintainer it may interest you)

For a temporary solution: please make sure setuptools-scm is installed in the environment you're installing Black to, if that fails, make sure to have setuptools-scm installed AND install black with --no-build-isolation

---

\cc @cooperlees we need to publish a release with wheels ASAP IMO, how is the CHANGELOG entry verification process coming along?_

edit: Cooper, I would love if you could pin this issue since it looks like we're gonna see quite a few more of such reports

okay, the issue was that setuptools was borked, version 51.3.1 works so yeaaah. but a new release would be nice since wheels are still easier to install

[vint21h]

Suddenly it starts working without any changes on my side, at localhost using pip/pipenv and at GitHub actions using pip.

[reata]

My GitHub Actions is back to normal with setuptools==51.3.1 released just now.
This seems related to setuptools==51.3.0 release 2 hours ago because my build was successful yesterday.
See https://pypi.org/project/setuptools/#history

[ichard26]

You seem to be correct, @reata thanks for looking at setuptools again because I didn't notice that even though I suspected a setuptools release mishap.

[amanda-wee]

Confirmed back to normal with Github Actions

[JelleZijlstra]

Sounds like this was due to a broken setuptools release. Is there anything for Black to do or should we close this issue?

[ichard26]

Seems reasonably safe to close this so I'll do that. We could ban that broken version of setuptools in our build requirements configuration in pyproject.toml but that's most likely useless as the build environment will contain the newest setuptools anyway.