KeyError: 'home-page' with importlib_metadata 8.0.0

[FeodorFitsner]

Is there an existing issue for this?

• I have searched the existing issues (open and closed), and could not find an existing issue

What keywords did you use to search existing issues?

No response

What operating system are you using?

Linux

If you selected 'Other', describe your Operating System here

No response

What version of Python are you running?

Python 3.10.13

How did you install twine? Did you use your operating system's package manager or pip or something else?

pip install twine

What version of twine do you have installed (include the complete output)

5.1.0

Which package repository are you using?

pypi.org

Please describe the issue that you are experiencing

importlib_metadata has just released 8.0.0 and CI jobs calling twine upload started failing with the following error:

Traceback (most recent call last):
  File "/home/appveyor/venv3.10.13/bin/twine", line 5, in <module>
    from twine.__main__ import main
  File "/home/appveyor/venv3.10.13/lib/python3.10/site-packages/twine/__init__.py", line 40, in <module>
    __uri__ = metadata["home-page"]
  File "/home/appveyor/venv3.10.13/lib/python3.10/site-packages/importlib_metadata/_adapters.py", line 54, in __getitem__
    raise KeyError(item)
KeyError: 'home-page'

Please list the steps required to reproduce this behaviour

pip install --upgrade setuptools wheel twine poetry tomlkit virtualenv

Anything else you'd like to mention?

No response

[gesslerpd]

See #1124

[jykr]

Would be helpful to have twine 5.1.0 yanked from pypi to prevent CI's relying on twine being broken, until bug gets fixed

[henryiii]

Why does 5.0 work? Was the bug added to 5.1 just before importlib-metadata 8 was released? I was about to reply that it didn't have anything to do with 5.1 but checked it and it seems 5.0 works with importlib-metadata 8 (I assume).

I don't see the __init__.py file even being touched: 5.0.0...5.1.0. But the environment clearly does have importlib-metadata 8.0 and it works for me.

[henryiii]

Ahh, I see it; it's due to the modernization of the build system, and the new build system doesn't set home-page (it's triggering on twine itself!), but it happened to pass due to importlib-metadata returning None here instead of erroring before 8.0.

So yes, yanking 5.1 while waiting for 5.1.1 would be a temporary fix. You can also set !=5.1.0 in your CI's, like pipx run 'twine!=5.1.0'.

[jaraco]

This issue isn't due to a release of twine but due to a release of importlib-metadata 8. See #977 where the deprecation warning was detected and reported.